METHOD FOR ESTABLISHING A CONNECTION BETWEEN A SOURCE TERMINAL AND A DESTINATION TERMINAL, NETWORK N

专利摘要:
method for establishing a connection between a source terminal and a destination terminal, network node to a core network, access connection point of a core network, electronically readable data carrier, and, computer program product. the invention concerns the establishment of a connection between a source terminal and a destination terminal. both terminals can connect via the same access network. the access network accesses the core network through an access connection point. the access connection point transmits and/or receives connection establishment signaling along a signaling path through the at least one core network. using an information element in connection establishment signaling, information about access needs in the media plane of nodes in the signaling path is collected and provided, to determine whether a local path of a media path can be established in the access network .
公开号:BR112012003294B1
申请号:R112012003294-1
申请日:2010-08-13
公开日:2021-06-22
发明作者:Dirk Kampmann；Philip Hodges；Karl Hellwig
申请人:Telefonaktiebolaget Lm Ericsson (Publ)；
IPC主号:

专利说明:

technical field
[001] The present invention relates to a method to establish a connection between a source terminal and a destination terminal. The invention further relates to an access connection point and a core network node involved in establishing the connection, and the methods performed on these network nodes. Fundamentals
[002] Call setup is a standard procedure performed in a mobile terminal communication network. The establishment procedure is started after a connection request from a terminal (T0 origin terminal), such as a mobile terminal telephone or any other type of mobile communication device, which in general connects via a radio access network. A radio access network controller, such as a Radio Network Controller (RNC) of a UTRAN (UMTS Terrestrial Radio Access Network) or a Radio Base Station Controller (BSC) of a radio access network ( 2G RAN, switches signaling traffic with an access connection point, such as a Mobile Terminal Switching Center (MSC) of a core network. This so-called source access connection point (O-AGW) sends connection establishment signaling through the core network to a destination access connection point (T-AGW), which communicates with the destination terminal ( Tt) via a target radio access network. The signaling path (also called call forwarding path) from the O-AGW to the T-AGW which runs in the so-called signaling plane can pass through additional nodes of the core network, in particular control nodes controlling media connection points such as additional MSCs or the like. The nodes of the core network through which a signaling path carries out control of media connection points, whereby a media path is established in the media plane, also called the user plane, across the core network. The media path further extends from the MGW of the O-AGW and the T-AGW through the respective radio access networks to the originating terminal and the destination terminal, respectively.
[003] A signaling plan established through the access connection points and control nodes carries signaling traffic, while the media plan established through the media connection points carries media content such as voice data , video data or other types of user data. There are several methods of establishing a connection upon receipt of a request from a terminal, one of which is described in detail further below with respect to Fig. 6. In general, the O-AGW sends an establishment message to the T -AGW, with control nodes on the signaling (or forwarding) path instructing their associated media connection points (MGWs) to establish at least part of the media path.
[004] After receiving the establishment message and exchanging signaling traffic with the destination terminal, the T-AGW sends a response message to the O-AGW to finish the establishment of the media path, through which a ring tone back can be broadcast.
[005] The media path in general comprises a front channel (or "Channel UM"), which carries media contents in one direction from the MGW of the source AGW to the MGW of the destination AGW, a direction mentioned also being downstream call. The rear channel (also called “Channel B”) carries media content from the MGW of the destination AGW to the MGW of the source AGW, the mentioned direction also being called upstream. Downstream can also be defined as a transmission direction of a connection establishment message and upstream as a transmission direction of the reply message. Note that in art, the terms upstream and downstream are not always used in the same way. The particular meaning may need to be derived from the context in which the terms are used. As an example, downstream with respect to channel B may correspond to the upstream direction mentioned above, as contents are transported in the reverse direction on channel B.
[006] The terms downstream and upstream can also be used to define a relative position of a node in the signaling path or in the media path. As seen from a node on the path, an upstream node may be a node preceding the node mentioned in the path and a downstream node may be a node following a node on the path with respect to a transmission direction of a particular message or contents. In such a context, an upstream (or downstream) node may be different when viewed from channel A or channel B.
[007] In some networks, the nodes of the core network establish the front channel when receiving the setup message and the rear channel when receiving the reply message. In other networks, the nodes of the core network establish both channels upon receipt of the set-up message, with the addresses of the receiver of the media connection points being exchanged between the control nodes via inter-node signaling (so-called “Fast Path”).
[008] In other scenarios, such as visiting terminals from other networks, a media and signaling path can be more complex. As an example, additional core networks, transit networks and the like may need to be traversed to reach a particular operator's core network. The radio access network of the originating terminal can, for example, be connected to an originating core network, and also via one or several transit networks to an operator's core network. A network through which a core network is accessed may be called an access network. It can thus be a RAN, another core network, or the like.
[009] In conventional network architectures, the media path is established through the radio access network and possibly additional access networks and the core network in call setup and maintained throughout the duration of the call. Any node in the media path has access to the media plan, it can for example read data from the media plan (eg for multi-party conference or for call storage) and it can write or input data into the media plan (eg For multi-party conference or announcements). Such supplementary services generally reside within the core network and can take advantage of such simple access to the media plane.
[0010] In some countries and networks, the number of voice calls that originate and terminate within an area (eg city or region, also called local calls) may be relatively high. Two terminals can even reside within a radio cell. In terms of connection costs, connecting to such a cell is more properly expensive, this can occur eg. through microwave links or even via satellite.
[0011] In order to reduce connection costs, it is desirable to identify such calls and to provide a media path shortcut within the radio cell or radio access network, without using the entire media path through the core network . Such a media path shortcut can be called “local call local switching (LCLS)”. Users can benefit from providing such shortcuts as more direct routing of media content can provide higher voice quality and lower voice path delay, while at the same time, the network operator can benefit from the expense of reduced operation. A media path shortcut may also be called a “local shortcut”.
[0012] With respect to a local shortcut, the problem arises that some of the nodes in the signaling path may require access to the media plane. If such a shortcut is switched, then nodes in the access network may no longer be able to access the media contents, i.e. read or write to the media plane. When configuring the connection, it is often not, of course, clear that supplementary services need to be provided by the nodes in the signaling path. Services such as lawful intercept, home network recording services, tone insertion and advertisements generally require access to the media plan, preventing shortcut locations. It is therefore desirable to improve the end-user experience, such as distortion delay, etc., and reduce operator expenses, such as resource capacities and link capacity required, by improving local shortcut switching. In particular, the number of situations, in which local shortcuts can be switched, should be increased. It is desirable to determine the situation in which a local shortcut can be established. In addition, it is desirable to determine the media plane access needs or requirements of the nodes in the signaling path.
[0013] It is thus an object of the present invention to prevent at least some of the above disadvantages and to improve the establishment of connections in a mobile communication network. summary
[0014] According to the first aspect of the invention, a method of establishing a connection between a source terminal and a destination terminal in a mobile terminal communication network is provided. The source terminal and destination terminal connect via an access network, which accesses a core network through a source access connection point to the source terminal. For the target terminal, it can access the core network through a target access connection point, which can be the same or different source access connection point. At the originating access connection point, an information element is included in a setup message to establish the connection through at least the core network. The setup message is then transmitted on a signaling path through at least the core network to a destination access connection point in the core network. There may still be networks involved in the signaling path. At least one of the nodes through which a signaling path progresses enters information into an information element relating its needs to access a media plan of the connection to be established. The setup message comprising an information element is received at the destination access connection point. The response message including the information element with the collected media plane access needs is transmitted in the opposite direction along a signaling path to the originating access connection point. Information about the media plane access needs of the nodes in the signaling path collected through the information elements is then provided to determine whether a local path of a media path of the mentioned connection can be established in the access network.
[0015] The possibility of establishing a local media path shortcut can thus be reliably detected, which can result in an improved user experience and a reduction of required resources. Furthermore, it may be possible to differentiate between different situations with different supplemental services requiring access to the media plan, such that shortcuts can be provided in more situations.
[0016] According to an embodiment of the invention, nodes in the signaling path capable of processing the information element, ie enabled nodes, adapt the media routing through their respective media connection points on the basis of their own access needs the media plan and also the needs of access to the media plan of the other nodes in the signaling path. Enabled nodes can obtain this information by means of an information element included in the setup message and/or in the response message. Resources can thus be saved if only certain nodes in the signaling path have media plan access needs.
[0017] In some embodiments, the information element can always be included in the setup message in order to reduce the number of missed possibilities of providing a shortcut. In other embodiments, the information element is selectively included. The source connection point can verify that the source terminal and the destination terminal connect via the same access network. This can occur by retrieving information from a common visitor location record (VLR) storing information about terminals connecting via the access network or receiving information about terminals connecting via the access network from a control node of the access network. access. This can also occur through a selection-based number analyzing a receiving party's number for whether it is of a type that connects via the same access network. The information element can then only be included in the establishment message if the source and destination terminals are connected via the same access network. Excessive signaling overhead can thus be reduced.
[0018] There are different possibilities to establish the information element. As an example, the media path can comprise a front channel and a rear channel. An information element may then comprise at least the following elements indicating a need to access the media plane: an element indicating a need to read the front channel, an element indicating a need to write the front channel, an element indicating a need to read the rear channel and an element indicating the need to write on the rear channel. It may thus be possible to obtain a comprehensive overview of the access needs of nodes in the signaling path.
[0019] The information element may comprise elements in the form of flags to store media plan access needs. A node can then introduce information into the information element by setting the flag for the corresponding need to access the media plane. Flags require small storage space and can be read easily.
[0020] The media plan access needs of each node that introduced such information can be stored separately in the information element, for example in association with a node identifier for the respective node. Entry of information into an information element can also occur through an enabled node not writing any access needs into the information element and by means of indicating that there is no access need, or simply entering a node identifier in the information element. By storing the information separately, the access needs of each node along the path can be identified, and furthermore, nodes that are not able to process the information element can also be identified.
[0021] It is also possible that each node enters the information in the information element setting the same flag for each need to access the media plane. If a particular flag is set by a node, subsequent nodes may not reset the flag. The information element transmitted along a signaling path can thus accumulate the need for access to the media plane of the nodes enabled in the signaling path. The information element can thus be kept compact.
[0022] In one embodiment of the method, nodes in the signaling path can establish the media path at least through the core network upon receipt of the setup message and/or the response message by configuring the connection point context of media and the links of their respective associated media connection points (MGW). The media path can thus be fully established and ready for transporting traffic. Based on the accumulated media plan access needs, it is then determined whether media contents are to be streamed on the configured media path at least across the core network. As an example, if an information element indicates read access to a particular channel of the media path, media contents are broadcast on that channel. Traffic on the core network can thus be reduced and resources can be saved. Media contents can be bifurcated, eg. on the access network or on the access connection point to provide both a local shortcut and read access.
[0023] In another embodiment, the media path is similarly established at least through the core network upon receipt of the setup message and/or the response message. Enabled nodes can then be configured to decide to establish an upstream or downstream link of the media path to passive based on the media plane access needs of the upstream or downstream nodes in the signaling path. Setting a link to passive means that resources for the link are still allocated and no content is transmitted over the link. Consequently, content can only be streamed to nodes on the media path that have a need to access the media plane, further reducing traffic on the core network.
[0024] If the media path comprises a front channel and a rear channel, this can for example be done as follows. The destination access connection point may include an additional information element in the reply message. The enabled nodes through which a signaling path progresses enter information relating their need to access the media plane into the additional information element of the response message. An enabled node on the signaling path can then determine from the information element received with the set up message whether any downstream back channel nodes have media plane access requirements for the back channel. Similarly, from the additional information element received with the response message, the node can determine whether any downstream front channel nodes need access to the media plane for the front channel. If there are no nodes of the respective downstream channel with access needs, the node can instruct its associated media connection point to set the respective channel downstream of the link to passive. Thus, the node can no longer transmit media contents on the respective downstream channel, thus reducing traffic and saving resources. This method can be performed in particular if no node on the signaling path requires write access. If write access is required, the downstream rear channel can only be set to passive if upstream rear channel nodes have no need to write to the rear channel, and the downstream front channel can only be set to passive if upstream front channel nodes have no need to write to the front channel. Consequently, if the first write access node comes before the last read access node, all links in the channel can be set to active.
[0025] If no content is transmitted over a link established to establish the media path over a certain period of time, a disconnect may be triggered for the link. This can be avoided by transmitting a heartbeat signal over such a link in the media path. It is also possible to disable detection of whether media contents are transmitted over these links in the corresponding media context manager of the media connection point that provides the respective link. The media path can thus be kept on hold in case content needs to be streamed over the core network, e.g. after a required spontaneous read access.
[0026] In another embodiment, enabled nodes can make use of an additional similar information element to determine upstream nodes and downstream nodes having media plane access needs. If an enabled node determines that any nodes in the signaling path have no need to access the media plane for the respective channel (eg front channel or rear channel) on the basis of the information element and the additional information element, then the node does not establish a link from the media path to the next node downstream of the respective channel, or removes a link from the media path already established to the next node downstream of the respective channel. How the links are or are not by media connection points can be reduced. Additionally, as unused links are not configured or are removed, there may be no need for a heartbeat signal or for not enabling content transport detection. If write access is required, then links may just not be established or removed if upstream nodes of the respective channel have no need to write to the respective channel.
[0027] Legacy network nodes on the signaling path that are not able to process the information element, i.e. non-enabled nodes, can still be detected. In general, detection can occur by enabled nodes analyzing the information element received with the establishment and/or response message for nodes on the path that have not entered any information in the information element, in which each of the enabled nodes can put example enter an identifier.
[0028] In a particular example, the information element may comprise a node identification field, in which each enabled node enters a node identifier. An enabled node can then check whether a node identifier stored in the node identification field of the information element received with the setup message matches a node identifier of the node from which the message was received. If the node identifier does not match, the node can establish full need for access to the media plane in the information elements. This way it can be ensured that the legacy node has full access to the media plane. The enabled node can then write its own identifier in the node identification field of an information element. The information element can be overwritten at any time in order to reduce the required storage space and consequently excess signaling. A simple but effective legacy node detection can thus be performed.
[0029] Furthermore, by using an additional information element in the response message or by overwriting a node identifier in a node identification field, it is certainly also conceivable to store in the information element separately for each enabled node the respective access needs to the media plan and a node identifier.
[0030] In the additional mode, the information element comprises a list of access access needs in which each enabled node of the signaling path enters its need to access the media plane and a node identifier. Enabled nodes can then establish the media path as follows. A node that itself has a need for media plane access may establish a direct connection (i.e. a media path connection) to the next upstream or downstream node that also has a need for media plane access. The media path can thus bypass nodes other than the source and destination access connection points that do not have any need to have access to the media plane. Traffic on the core network can thus be reduced, and skipped nodes can save resources.
[0031] A node capable of processing an information element, ie an enabled node, which has a need for access to the media plane can scan the list of access needs comprised in the information element of the response message for the first node to downstream or upstream in the signaling path that has a need to access the media plane. This can then establish a media path connection to the first detected node or change an existing media path connection in order to connect to the first detected node if such a node is found. The media path can thus be at least configured on the core network. This can be done regardless of the media channel to which an access need is detected, or it can be done by media channel.
[0032] Legacy nodes in the signaling path can be detected by analyzing the information element. As an example, if a node from which the message with the information element is received has not entered its identifier in the list, it can be assumed that the node is a legacy node. If one or more legacy nodes are detected, a media path connection can be established from the legacy node to the first enabled node upstream and the first enabled node downstream in the signaling path. Additionally, media path connections can be configured from the first upstream and downstream nodes to the legacy nodes in order to establish the legacy nodes in order to establish the media path through the legacy node. As an example, the first upstream and/or downstream enabled node can fully subscribe to the media plan, ie introduce full need for access to the media plan in the information element, such that establishing connections through the legacy node of the network , it can be ensured that the legacy node gets full access to the media plane.
[0033] The information about the need to access the media plane of the enabled nodes that is collected with the information element can furthermore be evaluated in order to determine whether the local path media path can be established in the access network. Such an assessment can be carried out by one or both of the access connection points. If such a shortcut can be established, an access network controller can be informed that the shortcut can be established or information about the need for access to the media plane can be transmitted to said controller. Based on the information received, the controller can then decide to establish the shortcut itself or instruct other nodes to establish the shortcut.
[0034] According to a further aspect of the invention, a method of establishing a connection between a source terminal and a destination terminal connecting via the same access network is provided. The access network has access to the core network through at least one access connection point. The method is performed by a node of the core network. The core network node receives connection establishment signaling to establish the connection which is transmitted at least along one signaling path in the core network. A signaling path passes through the core network node. With connection establishment signaling, an information element is received that stores the media plane access needs of at least one node preceding the core network node in the signaling path with respect to a transmission direction of the data element. information. Media plan access needs indicate the needs of a preceding node to access the media plan of the connection to be established. The core network node enters information relating its needs to access the media plane in the information element. The information element is then transmitted with the connection establishment signaling to a next node in the signaling path. The collection of media plane access needs from the nodes in the signaling path through the information element can thus be enabled in order to determine whether a local shortcut of the connection's media path can be established in the access network.
[0035] In one embodiment of the method, the core network node adapts media routing through its associated media connection point on the basis of its own media plan access need and media plan access needs of the other nodes on the signaling path. These needs may be indicated in an information element received with connection establishment signaling and/or in a corresponding information element comprised in the message received in response to connection establishment signaling. In this way, the core network node can save resources and can reduce traffic through the core network.
[0036] In an example, the media path may comprise a front channel and a rear channel. In addition to an information element received with a connection establishment signaling, an additional information element storing media plane access need of at least one node preceding the core network node in the signaling path with respect to a direction of transmission of an additional information element may be received with the corresponding reply message. Then, it can be determined from an information element and from an additional information element whether any node in the signaling path needs access to the media plane for the front channel or for the back channel. The core network node can then set the context of the media connection point and its associated media connection point's links so as to establish the media path through the core network. This can be done such that it is determined from the information element and the additional information element that there is no need to transport media contents from the front channel and back downstream, the media link downstream to the respective channel is not established, or if it was previously established, it is removed. It is also possible to set the media link downstream for the respective channel to passive, meaning that no content is transmitted over the media link. The core network node can then trigger the sending of a heartbeat signal over the passive link, or it can disable detection of whether media content is transmitted over the passive link in the corresponding context manager of the media connection point.
[0037] In another modality, the information element comprises a list of access needs in which each node enabled in the signaling path enters its need to access the media plane and the node identifier. With a response message for the connection establishment signaling, the information element with the list of access needs is received. If the network node has a need for access to the media plane of its own, it scans the list comprised in the response message to the first node downstream or upstream in the signaling path that has a need for access to the media plane. Then it sets up a media path connection to a first detected node or changes an existing media path connection in order to connect to the first node, if such a node is found. The media path at least on the core network can thus be configured. If it does not have any need to access the media plane, it can avoid establishing media path connections, such that the media path ignores it. The core network node can thus save resources as no context managers and links need to be assigned.
[0038] The information element can be configured as described above. In particular, it can comprise elements to indicate read and write access needs for forward and backward media channels, the elements can be provided in the form of flags, and the information element can store access needs in accumulated form or separately for each enabled node.
[0039] In addition, the method may comprise any of the steps described above with respect to the core network node. You can, for example, perform a detection of legacy nodes in the network by analyzing the information element, eg. comparing an identifier entered by the last preceding enabled node with an identifier of the preceding node in the signaling path.
[0040] According to a further aspect of the invention, a network node for a core network adapted to establish a connection between a source terminal and a destination terminal that connect via the same access network is provided. The access network accesses the core network through at least one access connection point. The core network node is configured to perform any of the methods mentioned above with respect to the core network node.
[0041] The invention further relates to a method of establishing a connection between a source terminal and a destination terminal connecting via the same access network, the access network accessing a core network through at least one point of access connection, the method being performed by the access connection point. In the method, connection establishment signaling to establish the connection is received, a signaling being transmitted along a signaling path at least in the core network. Information about the needs of nodes on the signaling path to access the media plane of the connection to be established is collected by retrieving an information element from the received connection establishment signaling. The information element stores the media plane access needs of at least one of the nodes in the signaling path. The thus collected information about the need for access to the media plan is provided to determine whether a local shortcut of a connection's media path can be established in the access network. By having this information available, a reliable determination of whether a shortcut is possible can be achieved, which in turn can result in an improved user experience and reduced operating expense if such a shortcut is established.
[0042] In one embodiment, the access connection point is an originating access connection point through which the core network is accessed for the originating terminal. The originating access connection point may then further include an information element in the set up message to establish the connection at least through the core network and transmit the set up message in a signaling path at least through the core network to a target access connection point on the core network. The connection establishment signaling mentioned above may then be a reply message which is transmitted by the destination access connection point in response to the establishment message. The response message can then comprise the information element of the setup message into which at least one of the nodes along a signaling path has introduced its need for access to the media plane. The access connection point can of course itself introduce its own need for access to the media plane into the information element before transmitting the establishment message.
[0043] In another embodiment, the access connection point is a destination access connection point through which the core network is accessed to the destination terminal. The set up signaling mentioned above may then be a set up message which is transmitted by the source access connection point of the core network along a signaling path and received by the mentioned destination connection point and comprising the element of information. The destination access connection point can then transmit the response message including the information element with the need to access the collected media plane in an opposite direction along a signaling path to the source access connection point . You can, for example, copy the information element received in the reply message. The destination connection point itself can of course introduce its own need to access the media plane into an information element before transmitting the response message. Any enabled node along a signaling path can thus be informed of access needs.
[0044] In a further embodiment, the destination connection point may include an additional information element in the response message in order to allow at least one of the nodes through which a signaling path progresses to introduce information relating to its need to have access to the media plan in the additional information element. Through the two information elements, nodes in the signaling path can determine whether upstream or downstream nodes need access to the media plane.
[0045] Again, the information element can be configured as described above.
[0046] In addition, the method may comprise any of the steps described above that can be performed by an access connection point. As an example, the access connection point can determine from the information collected with the information element whether a shortcut in the access network is possible and provide corresponding information to a control node of the access network.
[0047] As the access connection point can also be considered a node of the core network, it can still perform any of the steps described above with respect to the nodes of the core network. It can, for example, re-establish the media path from its associated media connection point to the next node in the core network.
[0048] A further aspect of the invention provides a corresponding core network access connection point adapted to establish a connection between a source terminal and a destination terminal connecting via the same access network. The access connection point can be configured to perform any of the methods described above with respect to an access connection point.
[0049] The invention further provides an electronically readable data carrier with stored electronically readable control information established such that when using the data carrier in a computer system, the control information effects any of the above methods.
[0050] In addition, a computer program product that can be loaded into an internal memory of a computer system is provided, said product characterized in that it comprises portions of software code to perform any of the methods described above when the product runs. The product may be provided on a data carrier.
[0051] It should be clear that the features of the aspects and embodiments of the present invention mentioned above and explained further below can be used not only in the respective indicated combinations, but also in other combinations or alone without leaving the scope of the present invention. Brief Description of the Drawings
[0052] The foregoing and other features and advantages of the invention will become further apparent from the following detailed description read in pool with the accompanying drawings. In the drawings, like reference numerals refer to like elements.
[0053] Fig. 1, schematically, illustrates the connection of a source terminal and a destination terminal via the same access network to a core network characterized by the fact that it comprises a signaling plan and a media plan .
[0054] Fig. 2, schematically, illustrates a signaling path and media path from a source terminal to a destination terminal through an access network in the form of a core network of the first operator and through the core network of a second operator.
[0055] Fig. 3, schematically, illustrates an information element according to an embodiment of the invention and its transmission in a signaling path through the core network.
[0056] Fig. 4, schematically, illustrates a possible implementation of an access network and a core network.
[0057] Fig. 5, schematically, illustrates a signaling path and media path through the core network having a source access connection point and a destination access connection point.
[0058] Fig. 6 is a flow diagram, schematically, illustrating a signaling when configuring a connection in the network architecture of Fig. 5.
[0059] Fig. 7 is a flow diagram illustrating a signaling when configuring a connection according to an embodiment of the present invention.
[0060] Fig. 8, schematically, illustrates the network architecture and the generation of ring tones in an embodiment of the invention.
[0061] Fig. 9, schematically, illustrates a network architecture and the generation of ring tones in an embodiment of the invention.
[0062] Fig. 10, schematically, illustrates a network architecture according to an embodiment of the invention characterized in that it comprises an additional core network node between the source and destination access connection points.
[0063] Fig. 11, schematically, illustrates a possibility of establishing a local shortcut.
[0064] Fig. 12, schematically, illustrates signaling between a source and destination access connection point in the core network when configuring a local shortcut according to an embodiment of the invention.
[0065] Fig. 13 is a flow diagram illustrating a method according to an embodiment of the invention.
[0066] Fig. 14 is a flow diagram illustrating a method according to an embodiment of the invention that is performed on a node of the core network.
[0067] Fig. 15, in schematic form, illustrates an access connection point according to an embodiment of the invention.
[0068] Fig. 16, in schematic form, illustrates a node of the core network according to an embodiment of the invention. Detailed Description
[0069] In the following description, the invention will be explained in more detail referring to the exemplary embodiments and the attached drawings. The illustrated embodiments relate to techniques for establishing the connection in a mobile terminal communication network, e.g. a mobile terminal communication network in accordance with the Technical Specification of 2G (2nd Generation) or 3G (3rd Generation). However, it is to be understood that the concepts as described herein can also be applied to other types of mobile terminal communication networks, e.g. WLAN (Wireless Local Area Network) networks, Wimax networks, LTE (Long Term Evolution) networks, and the like.
[0070] If two terminals, eg. user equipment (UE) such as mobile terminal telephones, computer terminals or the like connected to the core network via the same access network, it may be possible to establish a shortcut in the media plane in the access network. Such a shortcut must be in accordance with the requirements of the nodes on the regular signaling or forwarding path to access the media plane. In some circumstances, for example when read access is required, a shortcut can still be established, eg. forking media contents in the access network such that both shortcut and read access can be performed simultaneously. In other circumstances, for example when write access to the media plan is required, it may be determined that a shortcut is not possible. One problem is how the access gateway(s) in the core network determines the need for access to the required media plane of the nodes in the signaling path. This problem is general for all access networks that could have visiting terminals from other networks and use a circuit-switched (CS) signaling path through the network of core(s) to establish a shortcut connection between terminals connected in that network. Embodiments of the invention solve this problem by collecting the required information about the need to access the media plane at the access connection point using an information element transmitted with connection establishment signaling.
[0071] In general, access networks access the core network through access connection points. An access network can be any type of network, such as GSM (Global System for Mobile Terminal Communications), UMTS (Universal Mobile Terminal Telecommunications System) or LTE (Long Term Evolution) radio networks, but also networks WLAN / WIFI or “cable TV”, other operators' core network (eg connection via an international switching center), and the like to mention just a few examples.
[0072] The access connection point configures a signaling path through the core network. This is done to control the connection between the terminals. The actual content exchanged between the terminals (voice, etc.) is transported over a media path through the network of core(s). This media path would effectively not be required or could be shortcut when terminals connect via one and the same access network. Terminals can for example reside within the same radio access network.
[0073] Shortcuting within an access network, such as LCLS (Local Call Local Switching) on a GERAN (GSM EDGE Radio Access Network), can provide great benefits of both end-user experience (distortion, delay etc.) and operator capacity (resource capacity assigned in the sense of context handlers at media connection points and link capacity). In conventional systems, shortcutting should, however, only be done if the access connection points can ensure that none of the core network nodes involved actually need the context passing over the media plane. Examples of situations where this media access would be required are legal interception (read access), write services (read access) on the source network, tone insertion and advertisements (write access), etc. The access connection point usually does not have such information available.
[0074] The solution according to a modality is based on the following principle: the source access connection point (O-AGW) (ie the connection point via which the source terminal (To) connects) includes in the setup message via a signaling plane an information element, e.g. a registration field, whereby subsequent nodes through which the signaling path progresses can subscribe to the media content. Subscription means that nodes indicate a need or requirement to access the media plan, eg. read from or write to a particular channel in the media path. The establishment message can be any message that the originating connection point transmits to the destination connection point in the establishment process.
[0075] The destination access connection point (T-AGW) (ie the access connection point via which the destination terminal (Tt) connects to the core network) returns the accumulated subscriptions in the reply message ( eg by copying an information element in the reply message), which follows the opposite route to the originating connection point. Both connection points and all nodes within the path now have a view of media requests. Based on this information, it can be decided to have a shortcut within the access network, such as an LCLS. The reply message can be any message that the destination connection point transmits in the establishment process after receiving the establishment message.
[0076] Note that the source and destination connection points can be identical or combine in one device.
[0077] Shortcut is not necessarily prohibited when the node subscribes to media content, e.g. if you only need READ access. Media content may in that case be forked (copied) in the access network or access connection points such that the local shortcut can still be provided. Similarly, a shortcut can be established even if the node in the path requires write access. In such a case, media content from both streams (CN stream originating from node requiring write access and shortcut stream) may be mixed, eg. access network or access connection points.
[0078] The access connection points can always include an information element in the establishment message in order to determine if the nodes require the media plan. However this would not be required in all cases as only for a percentage of all requested connections a local shortcut would be possible. On the other hand, even if it is determined that a shortcut cannot be established, it may be possible to allocate fewer resources in the media path based on information in the information element (IE) which will bring benefits.
[0079] An example is the use of a global call reference number (GCR) by the originating connection point. The destination connection point can then easily detect that the origin connection point is in the same pool, or part of the same operator's network or even the same access connection point with the originator ID is part of the GCR number . For this, the origin connection point can always insert an information element. The destination connection point can then decide not to copy an element of information into the response when detecting that shortcutting will not be of benefit. The originating connection point and all nodes in the signaling path will acknowledge the absence and resume normal media establishment. Excess signage can thus be reduced.
[0080] By always including the information element, the circumstances in which the possibility of providing a media path shortcut is lost can be reduced. In the core network, various functions and services are known that can change the B number, i.e. the number of the party being contacted or called. Best known are call ahead (with mobile terminal to landline, landline to internet phone, mobile terminal to internet phone, satellite mobile to landline, etc.) and call deflection or selection as when calling a group number and a terminal that group is selected as the B part (or receiving party) which is common for company numbers. Another example is a forward-based area where a country wide number is translated into the B number of the store or agent closest to the national chain. And again, the agent or person at the store could have switched back to his mobile terminal because he's just making deliveries and no one is in the store. Thus O-AGW can in general only be sure about the whereabouts of party B (or called party) when it gets back the response and from this can retrieve that party B is effectively on the same access network. Based on this information and the access needs of nodes collected along a signaling path, a decision can be made as to whether a shortcut is possible.
[0081] The possibility of reducing traffic signaling traffic is to determine in advance whether a shortcut is in principle possible, and transmit the information element only if the shortcut is possible, i.e. selectively.
[0082] As an example, the origin connection point could be triggered by the access network (for example, by a controller in the access network) that a shortcut is possible. If both terminals connect via the same access network, they will usually connect via the same controller, eg. via the same base station controller (BSC), the same wireless network controller (RNC), the same eNode B, or the same international switching center. The access network controller (ACN) therefore has information available that they both connect via the same access network and can provide this information to the access connection point.
[0083] Another possibility is that the source access connection point itself detects that a local shortcut would be an option. An example is illustrated with access connection points in the form of two MSCs. Each MSC has a local warehouse (VLR: Visitor Location Record) containing details of the terminals connected via that MSC. An operator having an access network could have multiple MSCs, which could be grouped into a pool. Problem is that an MSC typically has no idea of the terminals connected to the other MSCs, which reside on the same access network. One possible solution is that local VLR's are in a database distributed over all MSCs (or all MSCs in a pool). Each MSC has its own local part of the VLR to which it reads and writes information. When writing information it is automatically copied on broadcast to all other MSCs to update their distributed VLR database. In this way, an MSC can check for a connection to be established whether the other endpoint is present in its own VLR or in one of the other MSCs belonging to the same network. The O-AGW can therefore determine if the called party is on the same access network.
[0084] The number of called parties can also be used to detect a common access network. It is still not always possible to see if the called party is of the same type that could be trapped in the access network. A particular problem is number portability, eg. where a fixed number is kept if a connection is moved from fixed connection to internet connection.
[0085] By the above means, the originating access connection point (eg MSC) can quickly detect the possibility of a local shortcut and initiate a signaling procedure through the core network(s). The destination connection point (eg MSC) automatically follows when it detects the presence of the information element and returns the accumulated response, i.e. the response message with the information element storing the collected media plan access needs.
[0086] To determine which option to use, the core network operator can weigh different factors, such as the percentage of calls that could have had a local shortcut (based on both parties on the same access network), the cost / usual effort or selective inclusion of the information element in a connection establishment signal, the gain by providing a shortcut, the percentage of cases where a local shortcut could have been established in principle (ie since both terminals connect via the same network access) but this was not possible as there was a node in the core network that required access to the media plan after all. Most of this data can be retrieved from the call data records stored in the accounting and billing system and/or settlement record of the inter-operator clearing houses. The operator thus has information available to decide whether always or selectively to include the information element, and what criterion/option to use for selective inclusion.
[0087] The information element that is transmitted with a connection establishment signaling, i.e. with the establishment message or the reply message, can be implemented differently. One possibility is to get simple media plane access requirements (or needs) "cumulative" into four simple flags: for two media path channels (Front Channel (FW) from To to Tt and Back Channel (BW) to from Tt to To), the following flags can be provided in the information element:
[0088] Need_Read_FW: yes / no
[0089] Need_Read_BW: yes / no
[0090] Need_Write_FW: yes / no
[0091] Need_Write_BW: yes / no.
[0092] If an enabled node on the signaling path has a need to access the media plane, it sets the corresponding flag to “yes” (or binary “1” or the like). If the flag was already set by a preceding node, it is no longer modified. Consequently, the four flags store the access needs of the enabled nodes for the entire media path. An advantage of such an implementation is its simplicity, and that the information field is not growing.
[0093] A further improvement can be achieved by providing these four flags per intermediate link between two nodes or separately for each node. Individual shortcuts may then become possible, such as ignoring one or more MGWs from the nodes in the signaling path through the network of core(s). Such a list provided in the information element would grow along the forwarding path and would require substantially more information, accumulated into a dynamically growing list of nodes.
[0094] In addition, a node identification field can be provided in the information element. There may be an individual field per node into which each enabled node enters its node identifier, or a single field may be provided that is overwritten by each enabled node along a signaling path.
[0095] Based on the information collected through the information element, it can not only be determined whether a local shortcut can be established, but also an adaptation of the media path through the core network becomes possible. As an example, if none of the nodes along a signaling path through the core network(s) have any access needs, the media path may not be established. On the other hand, if the node needs write access, a complete media path can be established. Even in cases where a local shortcut is not possible an adaptation of the media path on the core network(s) can be performed, resulting in reduced media traffic and resource savings. A signaling method as indicated in the following description will be further explained by means of four implementations for media plan handling, denoted as Basic detection (Media Plan kept hot standby), Media Plan Cold standby, Media Plan Reduced and Adaptive media forwarding. It should be clear that still implementations or a combination of implementation features are certainly conceivable.
[0096] A first implementation (hot standby) provides the access connection points with the ability to detect during the connection in progress if the internal node image requires WRITE access to the media content just observing the Media Plan, ie without interaction of the Plane Control Plan. The effective media path is fully configured and available even when unused. READ access that is spontaneously required by the node in the path is not detectable, so this method is not fully symmetric. Based on the access requirements collected by the information element, it can be determined whether media contents are to be transmitted over the fully configured media path. Since it is fully configured, the connection can be switched from the local shortcut to the media path through the core network efficiently, eg. if spontaneous write access is detected. As mentioned above, it is also possible to merge media streams when spontaneous write access, such that the local shortcut can be maintained.
[0097] A second implementation (Cold Standby) allows nodes on the signaling path (outer and inner nodes) to decide whether they should provide an active link or a passive link. Passive is defined not only for the link but also for the context manager at the media connection point. Passive means there is no content being streamed, only resources are assigned. In general this will free up substantial processing power and link capacity.
[0098] A third implementation (reduced media path) allows nodes on the signaling path to effectively reduce resources by not setting the media path to a succeeding node when no succeeding (or, for write access, preceding) node has subscribed. Biggest advantage is the reduction in resource usage. Negative aspect is that both hot standby and cold standby do not apply. Changes in the general media context could require establishing additional upstream media paths.
[0099] The fourth implementation (Adaptive media rerouting) allows nodes on the signaling path to reroute the media path not following the original signaling path. The node will make a direct media path connection to the next node that subscribed (i.e. needs access to the media plane), ignoring the MGWs of the nodes not having subscribed. This implementation brings further reductions in resource utilization and also reduces delays accumulated through media connection point (MGW) context managers and junction links. If the media context in general changes and will require modification for forwarding, this may be through establishing forwarding foreshadowing and switching.
[00100] One aspect to be aware of is that a passive media path, i.e. a link through which no content is transmitted, can provide some problems in MGW's context managers. Currently, they will trigger disconnection when for a certain period of time no media content is provided through them. A possible solution could be that media context managers have an adapted possibility to inhibit this detection. This will mean that the node actively has to remove this when the terminal for terminal connection is disconnected.
[00101] Another option is to apply a heartbeat signal on the passive links. An MGW configuring a link as passive also introduces a heartbeat into that link, eg. under control of the corresponding node of the core network. This has special advantages for the problem of not enabled nodes in the signaling path (nodes in the signaling path that have not been adapted to the possibilities of subscribing to media streams, ie not being able to process the information element), though that the heartbeat signal prevents them from going into the disconnected state.
[00102] Figs. 1 and 2 illustrate implementations of the invention in two different scenarios. In the scenario of Fig.1, the access network 101 is shown in general, it may be a radio access network (RAN) via which To and Tt connect to the core network 102. In the scenario of Fig. 2, a access network is a core network (CN) of a first operator via which To and Tt connect to a core network of a second operator. For the former, a local shortcut may be established in the RAN while for the latter, a shortcut may be possible in the CN of the first operator.
[00103] Fig. 1 shows the schematic view of a media path 150 through the core network 102 based on a connection request from a terminal To. Several internal nodes are involved in media path 150 denoted N1 through N4. These nodes can be control nodes controlling associated media connection points. Note that the control node and media connection point can be implemented on a single node or as separate nodes. The media path typically has two channels A (reference symbol 151) and B (reference symbol 152) as seen from the content release point by part A and B (source and destination terminals To and Tt respectively ). These channels are also called “front channel” (A) and “rear channel” (B) as seen from the call setup direction (= forward). Each channel is unidirectional, but the node can only request to read from it or write to it.
[00104] The diagram differentiates between a signaling plan 105 characterized by the fact that it comprises the control nodes (O-AGW, T-AGW and N1-N4) responsible for connection establishment and provision of supplementary services and the media plan 106 (also called user plan). The media plane 106 comprises the media connection points (MGW) that establish the media path in which content is transported on the core network 102. While in Fig. 1, the media path is schematically shown if extending from the last MGW directly to To or Tt, it should be clear that in an effective network architecture, a signaling path can pass through one or more nodes in the access network such as an access network controller (ACN) , for example. via a base station controller (BSC) and a base transceiver station (BTS) in a GERAN.
[00105] The originating access connection point (O-AGW 110) initiates the connection request with the establish message towards the first node N1 in the signaling path. This connection message can be a BICC-IAM, ISUP-IAM or the like. In the setup message an information element, e.g. in the form of a subscription signal byte as mentioned above, it is included. In the simplest form, it contains flags to subscribe read and write access to channels A and B. The flags can be denoted Ar (read access to channel A), Aw (write access to channel A) , Br, and Bw. The node wanting to subscribe to the Media Plan sets one or more flags when the establish message is sent in the forward direction along a signaling path. When a flag is already set, thus indicating a need to access the media plane, then the node does not change it. The information element thus accumulates the access needs of all enabled nodes in the signaling path. As mentioned above, other implementations of the information element are also conceivable.
[00106] The example flag byte is illustrated in Fig. 3, which is similarly applicable to the scenario in Fig. 2. In the example, the O-AWG includes the information element 200 characterized by the fact that it comprises the flags 201- 204 in the establishment message. O-AGW has no access needs and therefore does not raise any flags. Not raising any flags, he enters the information into the information element he does not need to access the media plan. N1 receives the message and also does not set any flags. N2 sets the Ar 201 flag (as indicated by the stripes), indicating the need to read the front channel. N3 sets flag Aw 202 and also wants to subscribe to Ar, but that flag 201 is already set so it is left that way. N4 does not set any flags but Ar and Aw are already set. Arriving at T-AGW the as-assembled flag byte is copied into the response connection message (as an ISUP-APN) and follows a signaling path in the opposite direction. If T-AGW has any access needs, it also enters that information into the information element before or after copying it.
[00107] Nodes no longer pick up the flags when the information element is transmitted in the opposite direction, but they can copy the accumulated result for their own purposes (if desired). Thus each node on the signaling path can obtain information about the access needs of all other nodes.
[00108] When the reply message comes, then each node configures the MGW context and links to the media path in some modalities. Nodes can, for example, establish channel A when receiving the set-up message and can establish channel B when receiving the reply message. By means of set-up and reply messages, the addresses of the receivers of the MGWs in the media path can be exchanged, allowing an establishment of the MGW transceivers with the receiver's addresses for the respective media channel. In other modalities, eg. fast path, MGW context and links may already be configured when the setup message is received. Receiver addresses can then be exchanged via inter-node signaling, e.g. a node on the signaling path informing an adjacent receiver node address of its appropriate MGW. Establishment of the media path can be expedited in such modalities. Finally the flag byte arrives at O-AGW. o-AGW and t-AGW can now decide on a shortcut or inform the access network controller that it can assign a shortcut. The final decision to establish a shortcut and establishing the shortcut can be made by ACN, as it then has all available information necessary to make such a decision.
[00109] The above methods can be performed in an environment in which all nodes in the signaling path in the core network are enabled according to the invention, ie they are able to process the information element entering their own access needs and can still be able to use the information provided with the information element to establish the media path according to an embodiment of the invention. The following options can be applied in situations where the absence of legacy nodes (unenabled nodes) in the network cannot be guaranteed, ie in which a legacy node may be present in the signaling path through the core network(s) .
[00110] A legacy node not updated to subscribe to media may still require access to media content, but would not be able to signal this. A possible solution to this problem is e.g. adding a node identification field (Node ID) to the information element (eg flag byte). An enabled node overwrites the ID field with its ID before passing it to the next node in the signaling path. The next enabled node checks whether the ID in the ID field matches the ID of the node from which it receives the request establishment message (ID of the originator of the message, same ID as where to send the reply later). If it doesn't match, then a non-enabled node was among them. The node then sets all flags (Ar, Aw, Br, Bw), independent of its own desire to subscribe or what it has received so far. In this way legacy nodes are treated as if they need full access to the media plane.
[00111] Another possibility is the use of selective areas in the establish connection message. Some areas are copied by each node as they contain information for all nodes in the signaling path. This typically contains information such as Global Call Reference, billing information for CDR's (bill data records) etc. The information element (eg the flag byte) can be provided in such an area of the establish connection message. Another type of area is an area that contains options. Example is media encoding, CAMEL supported etc. We will typically remove or adapt information in such an area as they do not always support the option. The information element may be included in such an area of the establishment and/or reply message. Entering e.g. a flag byte in such an area would cause a legacy node to remove the flag byte as an unsupported option. The presence of the legacy node in the signaling path can thus be detected. This method can detect legacy nodes in most cases. In one particular example, the flag byte is masked with a certain non-existent media encoding type. If a legacy node is present in the signaling path, the flag byte is not returned in the response message and T-AGW, and nodes 4 -1 and at the end O-AGW will recognize that a default media establishment may be required and that shortcutting may be infeasible.
[00112] It will be readily recognized that these legacy node detection methods will work similarly well with information elements other than a flag byte, e.g. with a list comprising separate access needs and node identifiers.
[00113] The steps of a particular modality of the methods described above are illustrated in the flow diagram of Fig. 13. The source terminal To requests a connection in step S1. The origin connection point O-AGW 110 initiates the connection request with a set up message towards the first node N1 on the signaling path in step S2. In the establishment message, the originating access connection point includes a subscription flag byte (step S3). The setup message is transmitted via a signaling plane, i.e. along the signaling or routing path (step S4). Nodes on the signaling path that receive and transmit the set up message configure one or more flags so as to subscribe to the media plan if they have corresponding access requirements (step S5). The setup message arrives at T-AGW 120 at step S6, which enters its own access requirements at step S7 and copies the flag byte into the response message. The response message is transmitted in the opposite direction along a signaling path (step S8), with nodes on the path configuring their MGWs according to the information received (step S9). The O-AGW 110 receives the response connection message with the flag byte in step S10. The O-AGW and T-AGW can now decide on a shortcut or inform the ACN of access network 101 if it can assign a shortcut, eg. transmitting the information collected about access requirements to the media plan.
[00114] In the following discussion, establishing the media path will be explained in further detail with respect to Fig. 1.
[00115] The basic detection method (hot standby) will still provide a full active media path through the core network. It is up to the AGWs 110 and 120 and ACN to make use of it either wholly or not or of just one channel, i.e. to determine over what channel media content is broadcast. This determination is made according to the need for access to the media plan collected with the information element. A “heartbeat” signal can be used in the Media Plan for unused channels to prevent the detection MGW's from disconnecting. Depending on the actual channel usage, a heartbeat can be sent from O-AGW to T-AGW on channel A 151 of the media path or from T-AGW to O-AGW on channel B 152 of the media path. As there may be non-updated nodes (legacy nodes) in the path, a traffic detection inhibition on MGWs should not be performed here in order to prevent a disconnection of these nodes.
[00116] “Hot standby” has the advantage that when general media context changes occur, the media path is still there and can be used immediately with spontaneous WRITE access. Spontaneous READ access is harder to detect.
[00117] However, if the first node or any other node will subscribe (eg N1 will subscribe to path A), path A will fully extend through the core network even when no other node has subscribed. In order to minimize the use of unrequested resources, the additional modality can be used.
[00118] An additional method to establish the media plan is “cold standby”. One problem is that the node knows from receipt of the flag byte that none of its predecessors on the signaling path have subscribed, but not whether later nodes on the path will subscribed. To solve this problem, the “forward direction” flag byte (in the establishment message from O-AGW to T-AGW) is copied to the reply message. Additionally, an additional information element is included in the reply message. As an example, a backwards flag byte can be added by T-AGW. Nodes on the reverse path do not take the flag byte in forward direction, but enter information on their respective media plane access need in the flag byte in backward direction in the same way they previously did the flag byte in direction. forward. In addition each node saved a copy of the flag byte in forward direction as received. When the reply message arrives, the node now has information available on the upstream node subscription and down stream and can thus set the MGW for a media channel to active or passive. Basically this means that it will not pass media content on upstream or downstream when no upstream node has subscribed for write access and no downstream node subscribed for read access. When arriving at O-AGW, these two flag bytes will be identical.
[00119] As mentioned above, in some modalities, the establishment of the initial link in the MGWs is done in the signaling direction. If there is Out-of-Band Transcoder Control (OoBTC) negotiation, then the Media Plan is anyway set after the APM backwards is received. This means that for the front channel, settings have been made but the setting for the context manager in MGW may need to be changed. For the forward channel this is not a problem as the link assignment is done upon arrival of the reply message. In other embodiments, both channels may be configured upon arrival of the setup message, so the setup for the context manager in the MGW may need to be changed for both channels.
[00120] The action to be taken simply refers to the received backwards and forwards saved flag byte. An initial setting of the MGW can be done upon receipt of the flag byte in the forward direction, indicating the access needs of the preceding nodes in the signaling path. When the backwards signal byte is received with the response message, information about the access needs of the nodes succeeding in the signaling path is available, such that connection establishment can be terminated. If the information elements (here the forward and backward flag bytes) evaluated at the node indicate that there is no need to transport media in a particular downstream, the node is an endpoint for the respective channel. This may, for example, be the case if no node of the respective upstream channel has a need to write to the channel and if no node of the respective downstream channel has a need to read the channel (if the node of the upstream channel does write access, content generated by that downstream channel node must be transported such that it can be merged into the shortcut media stream). This can then set the respective MGW link to passive, as no media content needs to be carried over the link. Instead it can transmit the pulse signal.
[00121] As an example, each internal node sets the context manager in its MGW upstream based on the flag byte in forward direction (transmitted from O-AGW to T-AGW) and vice versa. For sequence A B will be the flag byte in forward direction unless it indicates that any downstream node B has subscribed to it. For sequence A it will be the backward flag byte showing any downstream nodes that channel A has subscribed to. In case write access is required on either channel, the node can make use of both bytes of flags to determine whether the link for that channel is configured as active or passive. If request (i.e. need to access the media plane) has been established requiring transport of content in a particular direction, the media path is fully extended to the next MGW in that direction. If not, then this MGW is an endpoint for the respective channel. Content received is not yet sent. Instead a heartbeat signal is sent in sequence to keep the path active. Note that an MGW can be an endpoint for channel A or channel B or both. Each MGW is thus responsible for maintaining its downstream link a particular channel to the next active MGW.
[00122] Note that downstream channel B, which runs in reverse direction to channel A , corresponds to a "global" upstream direction, i.e. a direction from T-AGW to O-AGW.
[00123] As an example, node N2 of Fig. 1 is informed by the forward direction information element that nodes N1 and O-AGW have no need to access the media plane. Through the additional information element received with a response message, N2 is informed that downstream nodes, ie one of nodes N3, N4 and T-AGW, have read and/or written access needs for channel A, and that none of these nodes require access to channel B. As downstream channel A, access to media plane is required, N2 controls its MGW to transmit contents on the link from channel A to N3. As channel b downstream (towards N1 ), there are no access requirements, N2, configure the link from channel B to N1 as passive, eg. it initiates a transmission of a heartbeat signal instead of the media contents. Since no nodes have subscribed to channel B, all links of channel B in the 102 core network can be set to passive.
[00124] In “cold standby” mode, resources (such as links and context managers) are still actually assigned and cannot be used for other purposes. The advantage is that they are reserved and can be more safely activated by the signaling plane, i.e. by the respective control nodes. Similarly, Hot Standby also needs to support Signaling Plan for READ access.
[00125] An additional modality, the “reduced media path”, makes it possible to release these resources. The implementation of “shortened media path” is an additional improvement over “cold standby”. The same flag byte at first for up and down sequences can be tracked. Only now, if the node detects that it is an endpoint and has subscribed, it will assign a context manager but on the downstream link. Any downstream node detecting that it is an endpoint and not having subscribed, i.e. not having any access media plane access requirement, will not assign a context manager with its not having an incoming upstream link. And of course such a node will not establish a downstream link either.
[00126] For sequence B this can be done when receiving a reply message. For Sequence A, resources may first be configured (with an incoming message of establishment) but are discarded with the response received. A final establishment of the media path can avoid this. In other implementations, both channels may be configured when receiving a setup message, and consequently, links for both channels may need to be removed if there is no need for access of the respective downstream channel.
[00127] Since the links are not configured, resources can be released. When a change in the general context occurs the establishment of additional paths may be required. In the establishment of “reduced media path” establishment, the media path may extend through nodes (more precisely through their MGWs) that have not subscribed to the media plan. As an example, if N2 subscribed to channel A but N1 did not, the media path will still extend through the MGW from N1 to channel A. This will take up resources (such as links and context managers) that may not be used for other purposes. With the following modality (“Adaptive Media Forwarding”), those nodes can be ignored and media links can only be created between subscribed nodes
[00128] This mode uses a different information element than the single flag byte. Each enabled node in the signaling path adds its flags (i.e. enters its media plane access need) and its node identifier (id) to a dynamically growing list. Thus a connection establishment signal is building a downstream list of all enabled nodes with their subscriptions.
[00129] Like the previous implementation, the list received with the establishment message (which only understands the access needs of the upstream nodes) can be used to establish part of the media path (eg start media context), while the list received with the reply message, which also includes the requirements of the downstream nodes, can be used to finalize the establishment of the media path (eg complete the establishment of the media content and links). If the list indicates that there is no need to transport media content to the MGW of a particular node in the signaling path, the media path is configured in order to ignore this MGW.
[00130] As an example, Sequence A links may be initially configured and may be changed when receiving the list with the reply message. In other modalities, sequence A and/or B can be initially configured but needs to be adapted with the reply message characterized by the fact that it understands the complete list of access needs. In order to make correct media connections, the list can comprise the logical port/gate identification of the context manager for the different flags (or channels) in order to correctly establish the link. Presence of identification means having subscribed. As multiple links are present and the connection does not include a signaling request/response message, the global call reference can be used to identify the correct relationship. The logical port/gate ID can match the “Global IP (Internet Protocol) address and UDP (User Datagram Protocol) Port Number” by direction.
[00131] The steps performed by the core network node in the signaling path are illustrated in the flow diagram of Fig. 14. The setup message characterized by the fact that it comprises the information element with the list of access needs is received in the node of the core network (CN) in step S20. The CN node establishes the media path links / connections for sequence A / channel A in step S21. As noted above, fast or final establishment of the media path is also conceivable. The CN node enters its ID and its own media plane access need in the list (step S22) and passes on the establishment message with the updated list to the next node in the signaling path (step S23). The response message transmitted by the T-AGW and characterized in that it comprises the complete list is received by the CN node in step S24.
[00132] For sequence B, the node performs the following steps. When the reply message arrives, the CN node will avoid establishing the context manager and downlink (step S26) when it has not subscribed (decision in step S25). If it subscribed (step S25), it will scan the stored list from a request message to the first downstream node that subscribed (step S28). Then it will establish the downlink for that ID (or modify a previously assigned link correspondingly) rather then following the normal forwarding signal (step S29). The alternative is that a downstream node having subscribed establishes the connection to the first upstream node in the list that was subscribed and uses the logical port/gate ID along with the ID.
[00133] If sequence A was previously established, the procedure is slightly different. The node having not subscribed (decision in step S25) simply removes the context manager it previously assigned (step S27). When it is subscribed, a check is made on the assembled list of sequence B of the first upstream node that subscribed (step S30). The connection (i.e. the media path link) is then changed from the first node of the uplink to the first node having subscribed (step S31) using ID and logical port/gate information. Also here, final establishment of the media channel would facilitate this, as already established links do not need to be modified.
[00134] The CN node finally passes on the response message with the information element to a next node in the signaling path. This can of course also be done at an earlier stage in the method, eg. directly after receiving the reply message.
[00135] While the description of the above modality comprises the establishment of channel A with the establishment message and channel B with the reply message, the explanations are similarly applicable for a fast path establishment of the media path. Both channel A and channel B links established with the setup message can then be removed (steps S26 or S27) or adapted (steps S29 and S31 ) according to the need to access the media plan in the list received with the information element of the reply message.
[00136] With respect to Fig. 1 , if N2 has access needs and the list indicates that N1 does not have any access needs, then N2 configures the media path link of its MGW associated directly to the MGW of the O-AGW. The media path thus ignores the MGW of the N1.
[00137] In some arrangements, an MGW is only ignored if there is no need for access to any of the A and B channels, ie an MGW is not only ignored for the A or the B channel. The media path is thus the even for channel A and channel B. Other modalities in which channel A and channel B can take different paths are also conceivable.
[00138] Legacy node in signaling path can be treated as follows. As in the implementations described above, the first enabled downstream node detects the presence of at least one non-enabled node, from which it receives the establishment message. As a matter of precaution, the enabled node subscribes to both streams so it can provide/receive media content from both channels to/from the non-enabled node. The node preceding the legacy node (in the downstream direction) can similarly fully subscribe to all channels. In this way, two enabled nodes will create a normal path through one or a series of non-enabled nodes, the path having an enabled node at each end (i.e. the media path is created through the MGWs of those nodes). Nodes having subscribed for this purpose remember this and do not apply forwarding, but establish connections (i.e. media path links) as usual to the unenabled adjacent node.
[00139] Nodes enabled in the signaling path can be informed of the presence of a legacy node in the path as follows. The node (eg N3 of Fig. 1) detecting the legacy node (eg N2), for example notifying that the legacy node N2 has not entered any information into the access needs list, can enter this information into the list . When the response message arrives at node N1 preceding legacy node N2 in the downstream direction (ie the node from which the legacy node receives the set up message), it can determine from the list in the response message that a next downstream node N2 is a legacy node and establish the total media path links to this node. Upstream nodes additionally also receive the response message and acknowledge that N1 requires full access to the media plan as it connects to legacy node N2. Consequently, the media path will be established between the next upstream node that subscribed, and then through N1 to N2 and to N3. From there, the media path continues according to the adaptive forwarding scheme. It should be noted that the connections between nodes mentioned above refer to the media links between the respective associated media connection points.
[00140] With adaptive media forwarding, node MGWs not requiring access to the media plan can be ignored, resulting in a reduction in traffic and required resources. Note that adaptive media forwarding can also be performed if the information collected with the information element indicates that a local shortcut is not possible, eg. whether nodes on the signaling path have write access requirements.
[00141] Adaptive forwarding is also possible in case both terminals are not in the same access network. Adaptive forwarding is therefore a very powerful method of optimizing a media path. Any node on the signaling path may act as an O-AGW or T-AGW and may include an information element in an establishment or response message that is passed on by the respective node. Nodes in the signaling path capable of processing the information element can then make use of it in any of the ways described above in order to establish the media path.
[00142] As an example, the injection of the information element can be done by the destination AGW although the response message is not generated by that media connection point, but only passed on. It may introduce an information element copied from a setup message previously received into a reply message passing through and not comprising the information element. Similarly, the node on the path that is not the O-AGW can act as an O-AGW by including the information element in the passing setup message that does not yet comprise such an element.
[00143] Basically any node in the signaling path that detects in the establishment message that the information element is not present can inject it, as any node that does not see in the response message any returned information element can insert its local stored copy from the establishment message. This means that also parts or sections in a network, eg. a chain of signaling path nodes, can make use of the information element to optimize the media path.
[00144] Fig. 2 illustrates a different scenario in which the access network is a core network of a first operator, in which a local shortcut may be possible. The explanations given above similarly apply to the scenario in Fig. 2, with the nodes of the core network 102 performing the above methods.
[00145] The scenario in Fig. 2 can illustrate a call forwarding across a boundary. The calling party (or party A) with terminal To is roaming in operator 1's network (i.e. access network 101). To can connect via the radio access network (not shown) to access network 101. Traffic across the border between operator 1's network and operator 2's network is established through an international connection point exchange ( IGEX) on each side of the border. The IGEX on the access network works as an access network controller and can establish a media path shortcut between To and Tt, both of which also connect via the 101 access network. The IGEX on the core network works as a combined 0 / T-AGW and 0 /T-MGW. For operator 2, operator 1's network is seen as an access network. Operator 1 could also be an internet telephony operator, and IGEX could then be an IGW (Internet Media Gateway).
[00146] In the example of Fig. 2, the terminal To calls party Ti, the home network of which is a core network 102. At node N2, a call forwarding to Tt for calls received by Ti is provided. The media path is thus being established through the core network 102 back to the access network 101, and from there to Tt. The above methods, e.g. considering the collection of access requirements of nodes in the forwarding path and the establishment of the media plane can thus similarly be done in the core network 102.
[00147] If forwarding node N2 makes an announcement towards To that its call is passed on then that voice message uses the return media path to To. Therefore it is advantageous to establish the full media path (fast sequence). N2 may need interactive To input for call forwarding, eg. whether To will accept additional charges from the call side in forward direction. Core network services generally benefit from an established full duplex media path to the originating endpoint. To support faster establishment and thus allow interactive services, the downstream node receiving an establishment can directly contact its upstream intermediate node and inform it of its media receivers, and possibly available encoding means for the contents over the channel. media (inter-node signaling). Therefore, the complete media path can be established at call establishment.
[00148] In general, it is possible that the node needs to read / write in the establishment phase and not when the call is established. The node can introduce its access needs into the information element (eg the flag byte or flag list) when the setup message leaves the node (thus the service has already been applied). The input of information corresponding to the situation when the message enters the node can thus be avoided.
[00149] An even more complex case is what is called back to do service. An example is a collect call. The call is not established to the Tt terminal but the call first ends on the To-S service side, the service then calls Tt and asks for acceptance of the charge. If Tt accepts then the service joins the To-S and S-Tt sides of the call into a To -Tt path where a shortcut could be applied.
[00150] People with skill in the art will know how to modify and adapt the teachings for such specific cases. .
[00151] Fig. 15 shows a schematic block diagram of an access connection point according to an embodiment of the invention, which can be used in any of the above configurations. Access connection point 300 can be configured to perform any of the method steps described above with respect to any type of access connection point. The access connection point controls an associated media connection point via the MGW 305 interface, eg. to establish a media path through the core network. Therefore he can also perform any of the steps mentioned here with regard to establishing the media path. The access connection point 300 further comprises an interface 303 towards an access network, in particular towards a control node of such a network, examples include an interface towards a base station controller, a controller from a radio network or an eNode B of a radio access network or an interface towards the connection point of another core network, eg. towards an IGEX from another network operator.
[00152] Access gateway 300 further comprises a core network interface 304 towards nodes in the core network. This can, for example, interface with another access connection point in the core network or any other control nodes in the core network controlling media connection points. It can also interface with any other types of nodes as known in the art, such as a VLR or the like.
[00153] Transmit/receive unit 302 of access connection point 300 transmits and receives connection establishment signaling and other types of signaling via an interfaces, e.g. control signaling towards the MGW via interface 305. The processing unit 301 is adapted to control the operation of the access connection point 300 to carry out the steps of the method mentioned here. In particular, it can include the information element in the setup message or response message to be transmitted via the interface 304 and it can retrieve an information element from signaling received from connection set up and provide the collected information for a determination. whether a shortcut can be established. She can evaluate the information herself. It even controls its MGW according to the retrieved information to establish the media path, as outlined above.
[00154] The core network node (CN) 400 illustrated in the schematic block diagram of Fig. 16 is similarly configured with an interface 403 towards the core network nodes and an interface 404 towards the connection point associated media. Transmission/receiver unit 402 transmits and receives connection establishment signaling and control signaling via interfaces 403 and 404, respectively. The processing unit 401 is adapted to control the node of the CN 400, e.g. letting the node perform any of the steps of the method mentioned here with respect to the nodes in the core network. In particular it can extract and store an information element from the signaling signal received from connection establishment, introduce its media plane access needs into such an information element and forward connection establishment signaling including the information element via interface 403 to other nodes of the CN. It can further establish the media path through its associated MGW via control signaling on the 404 interface according to any of the modalities and implementations.
[00155] In the following discussion, specific examples of possible implementations of the invention are described. It should be clear that the explanations given above can be applied to the more specific implementations described later here.
[00156] An example of architecture comprises terminals in the form of mobile terminal telephones, access networks in the form of radio access networks (RANs) and access connection points in the form of a mobile terminal switching center (MSCs) . In general, a scenario for mobile terminal to mobile terminal calls may include an originating Radio Access Network (oRAN: it originates the call), an originating Core Network (oCN: with one, two, three or more MSCs and one or several MGWs), perhaps a Transit Network (TN: any complexity), a destination Core Network (tCN: such as oCN) and a destination Radio Access Network (tRAN). To provide a local shortcut on the access network, oRAN and tRAN must be identical, they must at least allow local shortcut. oRAN and tRAN can be logically different and can be controlled by different network operators who share the same physical RAN. In many cases only one MSC and only one MGW will be present, but the method can be applied to any number of nodes in the path. The method also has the ability to work with more than one Core Network and with any number of Transito Networks along the way (provided they are all updated to work according to an embodiment of the invention).
[00157] The first problem to be solved is to identify that two sides of the radio (the one coming from the mobile terminal of origin and the one for the mobile terminal of destination) belong together to a call. On the other hand, no local shortcuts are allowed. This problem can be solved by using a unique CallerID that is passed along the forwarding path from the originating side to the destination side. According to one aspect, it is possible to route the call in any arbitrary direction on this globe, therefore a true “global” CallerID is used. The existing “Global Call Reference” already in 3GPP can be re-used for this purpose.
[00158] Furthermore, it is negotiated along the call forwarding path that any node in the path allows the local shortcut. If a single node within the forward path does not comply with the local shortcut (either because it really needs to have access to the User Plan (ie Media Plan) or because it just doesn't understand the new procedure), then the Local shortcut may not be established.
[00159] In the present implementation, several types of a Local Shortcut are differentiated, combined with different access needs within the core network: b. the call is directly in the shortcut and the User Plan through the Core Network is not fully present. So no access to the User Plan is possible, no Complementary Services are possible - unless the Shortcut is broken and the Normal User Plan is established. This version has substantial improvements in terms of User Perception (high quality, low delay) and operating costs. This type of shortcut can be used on most calls and most of the time.c. the call is directly on the shortcut, but the User Plan data is still copied on the uplink (eg bifurcated) such that any node on the forward path can read the User Plan data. Sub-versions of this “read” functionality are that either the source-side uplink is copied or the destination-side uplink is copied, or both are copied. Media contents can thus be transmitted on one or both channels of the media path through the core network(s), depending on the access needs of the nodes in the path.d. the call is directly on the shortcut, but any node on the forwarding path can write to the User Plan and this data is sent to the mobile terminal. Sub-versions of this “write” functionality include writing towards the originating mobile terminal or towards the destination mobile terminal or both. During this writing time, the Local Shortcut is broken to feed the writing data to the mobile terminal. The solution according to the present implementation can allow to control all these cases with more efficient means. Upon call establishment, the first source MSC (oMSC) generates the "Global Call Reference" (GCR) and an Information Element called in this implementation "Need_Read_Need_Write" (NRNW), which comprises four binary flags: Need_Read_Forward: O: No , 1 : SimNeed_Read_Backward: 0: No, 1 : SimNeed_Write_Forward: 0: No, 1 : SimNeed_Write_Backward: 0: No, 1 : Yes
[00160] The oMSC configures these four flags within the NRNW as per its needs; the default is: all four flags are set to “no”, which maps to binary value “0”. The oMSC sends the GCR and NRNW forward to a next call forwarding node, i.e. a next node on the signaling path. This node (any node in the path) can modify these four flags as per its needs: Nodes are configured to never reset a flag from Yes to No. They can change any flag from No to Yes.
[00161] The potentially modified NRNW is sent forward along the forwarding path to a next node, until it reaches the tMSC, which can also change one or all flags to Yes (same rules). In the end, these four flags represent the logical OR function of access needs of all nodes along the way. In general the NRNW is sent in a backward direction along the forwarding path, at this time no modification is allowed. In the end, all Call Control Nodes in the path know the state of the User Plan's access needs, i.e. read access or write access is wanted/possible and in which direction (forward or backward).
[00162] The tMSC (and potentially also the oMSC) informs the associated tRAN (and oRAN) accordingly. In a possible case, all flags are set to “Yes” and Local Shortcut is totally prohibited. In the best case, all flags are set to “No” and Local Shortcut is totally unrestricted. All variants between them are possible.
[00163] During the call, the needs on any of these nodes can change and they can send a new Message in the forward/backward direction to update the NRNW Flags. The oRAN and/or tRAN are then informed and the Local Shortcut may need to be modified (partially or fully allowed or prohibited).
[00164] The information element (here NRNW) allows in the present implementation the control of all possible scenarios for the Local Shortcut and Complementary Services in establishing the call with efficient means. For in-call modifications, the same NRNW Information Element can be sent within an existing Message or a new Message. Switching between any Local Shortcut variants may be possible at any time.
[00165] In the following, an even more specific implementation of the above teachings is described with respect to Figs. 4 - 12. The implementation refers to a 2G or 3G network, and in particular to provide a local shortcut on a GERAN access network. The access network is provided in the form of a base station subsystem (BSS), which may comprise an access network controller in the form of a base station controller (BSC) and one or more base transceiver stations (BTS). ) communicating with terminals within range.
[00166] To avoid impacts to support the various types of complementary services (eg Conference Call, Explicit Call Transfer, etc.), and the support of Legal Interception procedures, not only the BSS (base station subsystem ), but also the access connection point, eg. an MSC, may be involved in establishing / releasing the local shortcut (also called local switching in the following discussion, or LCLS). In the present implementation of local switching, i.e. of providing a local shortcut in the access network, the BSS correlates the two sides of the call, i.e. it needs to know who is talking to whom. Left information is provided by MSC.
[00167] Local Call Local Switching (LCLS) may have greater impacts on the core network considering resource allocation in the MGW, potential procedures for removal/insertion of the MGW, linkage with complementary service control within the core network (eg. MPTY), Legal Interception procedures within the core network, Switching procedures without loss of communication, interaction with the MSC-S inquiry procedure, etc, as mentioned above. The present implementation for local call-local switching aims to keep an impact on the core network to a minimum, e.g. the impact on nodal functions, existing call flows, call establishment and call release.
[00168] In the following, all nodes on the “source side” are marked with a lowercase “o” character, such as oMS, oRAN, oMSC, oMGW. All nodes on the “destination side” are marked with a lowercase “t” character, such as tMS, tRAN, tMSC, tMGW, etc. The same nomenclature applies to all links, messages and procedures, where applicable, such as oA(-Interface), oAssignment-Request, etc. One direction of call setup signaling is called “forward”: oMS => oRAN => oMSC => tMSC => tRAN => tMS. The opposite direction is called “backward”: oMS <= oRAN <= oMSC <= tMSC <= tRAN <= tMS.
[00169] Figure 4 shows a Reference Architecture for the present implementation. It highlights only the main nodes and interfaces and differentiates between “source” nodes and interfaces (OMS, oBTS, oMSC, oAbis, oA) and “destination” nodes and interfaces (tMSC, tBTS, tMS, tAbis, tA). This also includes an Intermediate MSC and MGW (iMSC, iMGW), which can be a (G)MSC (Media Connection Point MSC) or other intermediate node of the controlling CN and its MGW. BSC, oBTS and tBTS are in the access network, here a RAN. The oMSC and tMSC access connection points and the CN node iMSC are in the core network. The BSC is a network access control node.
[00170] The “active” User Plan path (or media path) is shown with a solid line for the case that Local Switch is provided between two BTSes, while the “inactive” User Plan path, ie both Abis links, the two A links and the links within the Core Network are not carrying traffic and are therefore marked with dashed lines. The Control Plan (or signaling plan) is shown in a dotted line. Based on this Reference Architecture several call scenarios can be designed, eg. with the simplest scenario including just one BTS and one MSC, or a complex scenario including two different BTSes and more than two MSCs.
[00171] The following features can be provided for local call-local switching: Local call-local switching can be made transparent to the end user; Local call local switching can only be considered for voice call CS; Local switching of local call cannot prevent any additional services; Legal interception can be supported; The impact on the core network should be kept to a minimum, eg. the impacts on existing call flows, call establishment and call release; MSC in Pool may be supported.
[00172] Figure 5 shows the network architecture for this basic calling scenario. Only main signaling links are shown with dashed lines, the User Plan (i.e. media plane) is shown in solid lines. The call scenario here assumes that the “Early Assignment” option is used on both radio interfaces to achieve the best possible user perception in establishing the call. “Delayed Attribution” is discussed further below.
[00173] When the originating User (oUser) triggers the call setup, the oMSC interrogates the HLR (Home Location Register) and finds the tUser registered in the tMSC. Routing continues to and does not continue to and in tMSC; tMS is wanted. Once tMS has responded, the voice path is configured by oMSC sending oAssignment-Request and tMSC sending tAssignment-Request and both MSCs allocating all necessary resources in oMGW, tMGW and between nodes. Establishing these radio features takes considerable time and that is one reason for “Early Assignment”. Finally, when the User Plan is configured and ready for traffic, tMS triggers “Call Tone” to alert tUser and informs the CN with an “Alert” message. At that time tMGW starts generating tMSC command the “Call Back Tone”, which is sent back through the User Plan towards the oMS. Now tUser hears Call Tone and oUser hears Call Tone back until tUser accepts the call or oUser finishes the call attempt or another event happens.
[00174] Figure 5 shows the active User Plan and where it is still disconnected to prevent that modified mobile communication terminals could establish one-way communication or even two-way communication between users without accepting the call, ie without paying for a communication. Fraud would be possible.
[00175] Fig 6 illustrates the typical call flow for this MS to MS call with two MSCs with exemplary times, without LCLS. The negotiation of OoBTC (Out-of-Band Transcoder Control) in this example, here is based on BICC (Carrier Independent Call Control); SIP-I (Session Initiation Protocol) would be another valid alternative. Typically, tUser accepts after he hears the ring tone, finds his handset and decides the call is interesting enough. This can take considerable time; a considerable number of calls are never answered.
[00176] Note that in the present implementation, the User Plan that is already configured and especially the Abis Interface are carrying active traffic, because “Early Assignment” is assumed. So, oAbis and tAbis features are already in use, although User-to-User communication is not yet possible. Now tUser has accepted the call. tMS informs first of all tMSC by the message “Connect”. then tMS for Ring Tone, informs tUser with a display message “Connected”. tMSC reports tMGW; tMGW for Ringback Tone and connects through the User Plan in both directions. tMSC forwards the “Connect” message to the oMSC. OMSC informs oMGW; oMGW connects through the User Plan in both directions. oMSC forwards the “Connect” message to oMS; oMS informs oUser with a “Connected” display message. The call is now established, and users can communicate in both directions. These “Connect” signaling messages back from the tMS to the oMS and vertically to the MGWs (control plane) are in a “dispute condition” with the User Plan signal from the tMS to the oMS. If the Control Plane signaling is bit delayed, then tUser's first expressions are still blocked by tMGW and are lost, i.e. not heard by oUser. Typically the signaling within the Core Network part of the Control Plan and within the landline part of the BSS is fast and “luckily” the tMGW is reached very quickly. The User Plan across the radio sides is already set up and working (“Early Assignment”). There are no additional bottlenecks in the User Plan and connection is fast and comfortable for Users.
[00177] In the following, an implementation of LCLS implementation with two MSCs as access nodes is described. The implementation provides a local shortcut under the following conditions. Only if oBSS plus oMSC plus tMSC plus tBSS indicate support and acceptance for LCLS, and if oBSS is identical to tBSS, and if both sides of the call are identified by the BSS as belonging to a call, then LCLS is provided in this call scenario.
[00178] Existing Rel-8 architecture and signaling is assumed here, i.e. support of AolP on Interface A of the Control Plane and OoBTC / BICC or OoBTC / SIP-1 on Interface Nc and the corresponding MGW control signaling on Mc. The oMSC takes “Complete Layer 3 Message” oBSS capabilities and, “Call Establishment Request” by call side. The tMSC takes in the “Complete Layer 3 Message” the tBSS capabilities in the “Location Response” by call side. An excess of signaling within the CN can be minimized by the BSS informing the CN as early as possible about its capabilities considering the LCLS. The other direction, CN to BSS, seems less critical. These considerations and various options are discussed in detail further below.
[00179] The call setup example is described with respect to Fig. 7. It assumes that the BSSes signal their LCLS-Capabilites to the MSCs in both Layer 3 Full (CL3) messages; MSCs change a “Global Call Reference” within the core network to identify the call across all nodes. MSCs change an “LCLS-Negotiation”, eg. in the form of an information element, within the core network to check whether LCLS is feasible. The MSCs send this Global Call Reference and the result of LCLS-Neg to the BSS in both Assignment Requests. (t)BSS correlates call sides and reports LCLS status in tAssignment Acknowledge to tMSC and (o)BSS sends a new “LCLS-Notification” Message to oMSC at the same time. The MSCs inform the BSSes with a new “A-Connect” Message to connect the User Plan in LCLS. The MSCs inform the MGWs that no User Plan traffic is to be expected.
[00180] An Information Element is provided, both on Interface A and on Interface Nc. Some new Messages are provided on Interface A. They are marked by a gray shaded background in the Call Flow example of Fig. 7. For this MS to MS call with two MSCs, Fig. 7 illustrates a potential LCLS solution for the case that LCLS is doable. Trading OoBTC in this example, here it is again based on BICC.
[00181] From the earliest days of GSM, “Delayed Assignment” and “MS Generated Callback Tones” are valid options. Since in the User Plan it may exist during the phase hereafter Call Tone, if Delayed Assignment is applied, the originating MS can generate the Call Tone back locally. The core network informs the MS accordingly by the “Progress Indicator” IE within the message “ALERT” (for details see TS 23.108 and TS 24.008 of the 3GPP). Delayed assignment has several drawbacks and is not widely implemented, see below. Instead, Early Assignment is used and then - when the User Plan is already established - Ringback Tone generation takes place on the destination network side. The User Plan over a Core Network and through the originating BSS is used to transport the Call Tone back to the originating MS. The destination MGW can generate very different ringback tones (eg to identify a network/country, etc), also user specific ones (Custom Alert Tone feature requires this) and that makes this option attractive.
[00182] This however means that the source Radio, Abis interface, A- and Nb of User Plan is required and no savings can be achieved during the Ring Tone phase. In the context of LCLS this means: even if LCLS is possible later, after the ring tone phase, Abis resources are needed for a considerable amount of time and the cost-saving efficiency of LCLS is greatly reduced. It is therefore proposed in a present implementation of LCLS to consider using Early Assignment with MS-generated ringback tones to improve savings. The ringback tone variance can be more properly limited (which may be MS implementation dependent and could be improved), but User Plan resources can be saved during the ringback tone phase to CONNECT / Answer.
[00183] Figure 8 shows the User Plan during the ring tone phase, where Early Assignment is used to establish the Radio interfaces. In this example, the AbiS-, A- and Nb- interfaces are grayed out because they are not needed at this stage.
[00184] Signaling for call establishment with Delayed Assignment can be at first identical to signaling with Early Assignment - up to the point when the tMS is found and answered, the Selected Codec (SC) and the Codec of the Preferred destination RAN ( tRanC) are determined and the SC reported to the oMSC. The following description assumes that the local Ring Tone feature in oMS is applied. In the case of Early Assignment, radio and terrestrial resources are then allocated on both sides of the call. In the case of Delayed Assignment no resources are allocated at this point in time in the BSSes, but immediately Ring Tone is triggered in tMS and Local Ring Tone is triggered in oMS. No User Plan traffic is seen until tUser accepts the call. Figure 9 indicates this with gray shaded arrows on the radio, Abis and A links. The Nb links through the CN are allocated, but in the fact that no traffic is flowing and in the case of a packet switched CN, no load is generated.
[00185] Typically tUser accepts after he hears Ring Tone, finds his mobile terminal and decides the call is interesting enough. This can take considerable time; a considerable amount of calls are never answered. No User Plan costs are incurred up to this point. Now tUser has accepted the call. tMS informs the first of all tMSC by the “Connect” message. Then tMS for Ring Tone, informs tUser with a display message “Connected”, which is more properly anticipated. tMSC sends Assignment Request to tBSS; the tRadio side is set in the background, so tMSC tells tMGW; tMSC forwards the “Connect” message to the oMSC. OMSC sends Assignment Request to oBSS; the oRadio side is set in the background, so oMSC tells oMGW; oMSC forwards the “Connect” message to oMS; oMS informs oUser with the display message “Connected”. The call is now established, users can communicate in both directions.
[00186] These signaling "Connect" messages back from the tMS to the oMS and "southbound" to the MGWs are again (as in Early Assignment) in a "dispute condition" with the User Plan signal from tMS to WHO. But at this point, tUser typically starts conversation much earlier than the User Plan is set up and a substantial part of its early expressions may be lost. On a non-insignificant portion of calls, the User Plan cannot be established and the call attempt ends in failure. User experience of networks can thus be negative. The operator has a substantial cost advantage, but user dissatisfaction can be strong enough to be influenced by savings.
[00187] To overcome these disadvantages of Delayed Assignment, but still preserving as much as possible the positive effect a new mode is proposed here, called "Early Assignment - Delayed Abis Activation" or just in summary "Delayed Abis Activation". A signaling for call establishment with Early Assignment - Delayed Abis Activation is very similar and in many parts identical to a legacy Early Assignment signaling. Radio resources are allocated on both sides of the call. To achieve Delayed Abis Activation, MSCs inform the BSS in the Assignment Request of a new information element (IE) (or even just a flag within the LCLS-Preference IE) that (yet) no User Plan traffic is required . It then depends on the implementation within the BSS, how much User Plan savings are actually achieved.
[00188] In an All-IP transport plane, no IP traffic is seen and the statistical multiplexing gain is high, both within the BSS and on the AolP links. No Transcoder features are needed. In a TDM (Time Division Multiplexing) based transport plan, it is dependent on the BSS to allocate - or not - the Abis links. It is also dependent on BSS to allocate Transcoder resources - or not. Finally, the “Connect” message arrives from tMS to tMSC and oMSC. Then tBSS and oBSS are informed by the new message “A-CONNECT” in Interface A and the User Plan of the BSS is established, either with Local Switching, or with the User Plan through the core network. This User Plan establishment may only involve the landline parts of the BSS, the radio interface is already up and running and so the User Experience cannot be different to the legacy Early Assignment one. A signaling for LCLS can be assigned in such a way that Abis Delayed Activation is supported with minimal effort. Delayed Abis Activation may also be applicable for calls where LCLS is not feasible.
[00189] Figure 10 shows the network architecture for an example call scenario with three MSCs in the path. Only important signaling links are shown with dashed lines, the User Plan is shown in solid lines. In this example, an establishment is implemented to improve resource savings in both RANs: Callback Tone generated by MS and Delayed Abis Activation. No network-generated advertisements or other User Plan signals are used.
[00190] A number of call scenarios can occur to create multiple MSCs in the call chain, such as the call being routed to a subscriber that has user determined active supplemental services, “user determined busy call forwarding”, “forwarding no-answer call” etc. The call can be routed to a subscriber of another operator, who roamed the PLMN of the caller (Public Land Mobile Terminal Network) and BSS Service Area.
[00191] In the following example the call is assumed to be routed to a third mobile terminal (tMS2). When oUser triggers call setup towards tMS1 , oMSC interrogates the HLR (Home Location Register) and finds tMS1 registered in the iMSC. Forwarding continues to iMSC, call is located and “BUSY” indication is returned. In this example, iMSC detects that the call is passed on to another mobile terminal number, tMS2, which is registered in tMSC. Forwarding continues to tMSC and now tMS2 is found. Once tMS2 has responded, the voice path is configured by oMSC sending oAssignment-Request and tMSC sending tAssignment-Request and both external MSCs allocating all necessary resources in oMGW, tMGW and between nodes. iMSC is involved (or associated) with iMGW. It has to be noted that iMSC and iMGW do not have direct communication with the RANs and influence over LCLS needs to happen through the external MSCs. Due to this fact, use is made of the proposed “LCLS-Negotiation” through the core network as already discussed in the previous call scenario with two MSCs. Only if the iMSC understands (i.e. is an enabled node) and agrees to LCLS, is LCLS offered to the RANs in the present implementation. This case is assumed in the following discussion, e.g. iMSC does not need to have access to the User Plan.
[00192] Again establishing radio resources takes considerable time. Both external MSCs indicate to both RANs that Abis Activation is still suppressed (Abis Activation Delayed). The Global Call Reference is passed along with the LCLS-Preference to both RANs. Finally, when User Plan is configured within CN and Radio, Ring Tone within tMS2 is initiated and oMSC triggers Ring Tone back locally within oMS. The User Plan on Interfaces A and through the Core Network can be configured in this example, the block of MGWs blocks User Traffic, but it does not need to generate any messages or tones. RAN resources (Abis, TRAU, ...) can thus be saved. When tUser2 finally answers the call, a message flow and call establishment continues as in the example with two MSCs, the internal iMSC is just passing the CN signaling. The iMSC remains in the call path during full communication. Since the User Plan is locally switched (local shortcut) in this example, within the RAN and which is confirmed by the LCLS-Status notification (see above), there will be no User Plan traffic through the core network. All MGWs can be informed. This can take place according to any of the methods mentioned above.
[00193] In the following, a particular implementation making use of a GERAN access network is described. The implementation makes use of the following assumptions and considerations.
[00194] Local Switching re-uses existing Procedures, Messages and Information Elements (Rel-8) in Interface A as much as possible to keep impacts small. Local Switching re-uses the existing Architecture Division (Rel-8) between BSS and CN as much as possible. A common Local Switching solution supports AoTDM and AoIP and all combinations of them. Local Switching is applicable within a single BTS, but possibly also between BTSes. The implementation supports in Interface A all types of Local Switching within a BSS. The MSC may, however, not know in advance - without BSS signaling - whether or not Local Switching is possible, therefore the final decision whether to establish Local Switching or not is made by the BSS. Whether procedures and messages on Interface A for Local Switching are carried out independently on both sides of the call is dependent on the particular realization. Local Switching is established by the BSS through internal means, but only if it has gotten permission from the MSC(s) to do so. If the BSS receives signaling that for one side of the Local Switch radio is not or no longer possible, then the BSS does not establish Local Switch or breaks an established Local Switch.
[00195] The MSC(s) are responsible for linking the two radio sides together through appropriate means and finally submitting them to the BSS to allow to see the correlation. Local Switching does not (need not) involve transcoding between the radio sides, i.e. there is no need for Transcoders in the BSS. Transmission of in-band User Plan information (call back tone on call set-up and in-band announcement in the middle of the call) from the Core Network is supported. Local Switching is sometimes not possible, or needs to be released, eg. whether a Supplemental Service (Multi-Party Conference, Announcements, etc.) is required. MSC controls this. If certain complementary services for an ongoing call are required, implying that the User Plan over the Core Network needs to be (re)established, Local Switching may be broken by the MSC(s) after negotiation with the BSS. Switching without loss of communication between BSS is possible, leading to a stop or an establishment of a stop or an establishment of the Local Switch. Switching without loss of communication between MSCs is possible, leading to a stop or establishment of Local Switch. Switching without loss of Inter-System communication (eg 2G <=> 3G) is possible, leading to a stop or establishment of Local Switching.
[00196] If AoTDM is used, Interface A's TDM circuit can be released while Local Switch is established in the BSS (and after the BSS has informed the MSC). If AoIP is used, the IP link on interface A can be released while Local Switch is established in the BSS (and after the BSS has informed the MSC). In any case, User Plan transmission on interface A can be suspended while Local Switch is established (even if IP endpoint on sides of BSS and MGW are not released), saving bandwidth on AoIP interface is possible . Both BSS and/or MSC(s) sides are allowed to stop Local Switching at any time if necessary. If Local Switching has to be broken, this needs to be negotiated between BSS and MSC(s). Codec Type and/or Codec Establishment can be changed by the BSS autonomously after Local Switching is established, provided that same or compatible Codec Type and/or Codec Establishment are used on both sides of the call. However, the MSC(s) is (are) informed after the change. One possible exception is when AoIP with TC on MGW option is being used: this may trigger BSS's internal HO procedure and/or this may release Local Switching. Note that only Codec Types and Codec Settings provided by MSC(s) for both sides of the radio can be used. If two incompatible Codec Types and/or Codec Settings are to be used on both sides of the call, Local Switching is released early, i.e. this type of switching without loss of communication is not allowed while Local Switching is established.
[00197] Switches without loss of intra BSS communication can be performed by the BSS autonomously after the Local Switch is established. The MSC(s) are (are) informed after Switching without loss of communication about all changed parameters (Cell ID, Codec Type, whatever). DTMF tone transmission is supported. Charging aspects arising from Local Switching (if any) are considered in the standard.
[00198] The implementation makes use of the following considerations for the core network (CN). Any number of MSCs can be in the signaling path, and therefore impacts to the Nc interface are considered. Core Network Components (MSC Servers and MGW's) owned by different operators can be involved in a call that supports LCLS. Updated (LCLS-compliant) and legacy (LCLS-not-compliant) MSCs may exist in the path. All MSCs (nodes in the path) need to allow LCLS in this implementation. If a node denies LCLS (legacy MSC or intentionally), then all other MSCs are informed at call establishment and during the call and LCLS is stopped.
[00199] Legal Interception shall remain possible also when the Local Switching of call location feature is activated, and the main functionality shall remain in the core network. General requirements on Legal Interception are specified in 3GPP TS 33.106. In order to support the Legal Interception feature in the Core Network, user plan data for CS (circuit switched) voice calls to be intercepted needs to be transmitted to the Core Network, even if the calls are local. Possible implementations of a corresponding solution are detailed below.
[00200] In an implementation, whenever the MSC-S is aware that a local call needs to be intercepted, it does not allow the BSS to establish Local Switching in the BSS. The problem with this implementation is that it might not be possible to maintain the same end-user perception in all cases, in terms of end-to-end voice delay. The delay could in fact vary between “not locally switched, local calls intercepted” and “locally switched, local calls not intercepted”. This could happen, for example, in some scenarios where Local Switching of Local Call Resource would typically be implemented, i.e. whenever a satellite link is used to connect a group of BTS's to the BSC / MSC-S. In this case the delay for a locally switched call will be ~600ms shorter than for a normal call, unless an artificial delay is added for all locally switched calls (which is of course not desirable), and this difference would be easily noticeable by final user.
[00201] In another implementation, Local Switching is also allowed for intercepted calls, in order to maintain the same end-user perception in terms of end-to-end voice delay. This can be achieved if User Plan data is both locally switched and passed on to the core network in the same way, while User Plan data coming from an interface is downloaded on the BSS side. In order to support this, it may be sufficient to introduce a positional “Dual Transmission Required for MSC” Information Element in the new/modified BSSMAP messages used by the MSC-S to allow the BSS to establish Local Switching. This solution implies that some kind of indirect indication that the call will be intercepted will be transmitted to the BSS via some signaling message. However, interface A control messages containing this information can be protected (eg via IPSec) such that such information cannot be sniffed or tracked. An advantage of this implementation is that also for intercepted calls, LCLS is possible. The implementation can also maintain the same end-user perception in terms of end-to-end voice delay. Yet the implementation may require modifications on the BSS side because of the required dual transmission capacity and additional A-interface signal.
[00202] Particular implementations to address the user (or media) plan are detailed below. Local Switching Benefits of local call resources can be transmission bandwidth savings on the internal, Abis and Ater interfaces of the BSS. Establishing Local Switching in the present implementation means that either the call is switched in the BSC or a direct communication is created between the involved BTSs. In any case, the effect is that some resources in the BSS internal interfaces (Abis and Ater) can be saved. The specific solution will be based on the BSS network topology and remains implementation specific.
[00203] To minimize changes to existing AoTDM deployments and ongoing AoIP implementation, the impact on Interface A user plan handling is kept as low as possible in the present implementation. For AoTDM, no changes to the User Plan handling of the interface should be defined, even if the call is locally switched, the two corresponding circuits can always remain active, meaning that bandwidth savings on the interface for locally switched calls are not possible, but it is clear that bandwidth savings can be realized on the Abis / Ater interfaces. While the call is locally switched, TRAU will send some silent codeword on the interface. Also for AoIP, the two IP connections towards the MSC-S can always remain active, i.e. the corresponding IP endpoints may not be released. In any case, for AoIP it may be possible to suspend transmission in the user plan, and then save bandwidth, while the call is locally switched. Therefore, while the call is locally switched, the MSC-S (MGW) may not wait to receive data through the IP endpoints. It should be noted that this implementation may have an impact on the H.248 interface: the MSC-S may inform the MGW about Local Switch established and released such that the MGW may start and stop suspending transmission in the AoIP User Plan. For the case of AoTDM - Mixed AoIP (one side of the call using AoTDM, the other using AoIP), the proposal is again to keep the circuit and the IP connection active throughout the call. Whether User Plan data is sent over the IP connection while the call is locally switched could depend on whether or not a Transcoder is present in the BSS for this side of the call.
[00204] This implementation can simplify the procedures for establishing and releasing Local Switching in the BSS in call establishment and switching without loss of communication, n interface A and in the core network interfaces (eg for allocation / release of resources in the MGW ). As an added benefit, this approach can simplify in-band advertisement handling for a call that is locally switched, because with this solution, there is no need for eg. of re-establishing circuits or IP endpoints just to deliver the advertisement to the target user.
[00205] The BSS and CN must know their capabilities considering LCLS. To minimize over-signaling within the CN, the BSS can inform the CN as soon as possible. The other direction, CN to BSS, seems less critical.
[00206] One option would be to establish the BSS capabilities within each MSC by O&M parameters and the MSC capabilities within each BSS by other O&M parameters. So no additional signaling for the exchange of capability information is needed. However, this approach may require manual administration, yet the BSS as a whole must be homogeneously supporting LCLS or the LCLS attempt would fail quite often and will fail more often. This administrative approach is rather static and may not react quickly to changing conditions.
[00207] To overcome these inconveniences, the implementation can add a new information element (IE) (called “LCLS-BSS- Capability”) in the Assignment_Request_Response message. But this is a bit late in the process, the CN would have to do proactive signaling to LCLS without knowing if this would ever be successful.
[00208] An additional option is to add a new IE (named “LCLS- Capability”) on Interface A, on the call side, within the “Layer 3 Complete” Message. This is the approach already taken for AoIP capabilities. The same new IE could be used by BSS and tBSS. The MSCs would be reported at a very early point in time and by the call side, very accurately. This approach supports a non-homogeneous BSS, i.e. some parts of the BSS could (already) support LCLS, while others are (yet) not capable. This new IE can comprise at least one binary “LCLSY-Yes” / “LCLS-No” flag. Default is “LCLS-No” and this is assumed if IE is not present. A finer grain of this LCLS-Capability can also be implemented. One octet can be allocated for this purpose. OMSC would only start deploying additional signaling for LCLS if it knows that oBSS supports it. tMSC would only apply signaling to LCLS if it knows tBSS supports it. Through still selective signalling, e.g. a selective inclusion of the information element to collect User Plan access needs of the core network node, excess signaling in the core network can be reduced.
[00209] The access connection points, here oMSC and tMSC can consequently be informed (eg by the “LCLS-Capability” of the IE) that a local shortcut is possible in principle.
[00210] After the CN has taken the LCLS-Capability of both sides of the radio and has negotiated along the forwarding path that LCLS is feasible (see further below), it sends the result of LCLS-Negotiation within the assignment request to o BSSes. A new IE “LCLS-Preference” can be introduced, which is sent within the assignment request message from the MSC to the BSS on a per-call basis. This can instruct the BSS on the possibilities and preferences for LCLS for the call side.
[00211] The MSCs within the CN are not aware of the other end of the call-side or radio access network. They therefore still send a new Global Call Reference (see further below), which is unique to the call, within the assignment request for each BSS on a per call-side basis to allow correlation of the call sides of a call. , if both ends on a BSS. A new IE “Global Call Reference” can be introduced, which can be sent within the assignment request message from the MSC to the BSS on a call-side basis.
[00212] After the BSS has taken the LCLS-Preference and Global Call Reference and identified that LCLS is feasible, it reports the LCLS-Status in the Acknowledgment of Assignment message to the CN. Since both MSCs (oMSC and tMSC) send the assignment request at different points in time to the BSS, the LCLS-Status is only fully known and stable after the second assignment request (oAssignment-Request or tAssignment-Request, a that comes later). An additional new Message can be used, called “LCLS-Notification”, which is sent whenever the BSS detects that the LCLS-Status has changed. The MSCs use this LCLS-Status to determine how to handle the User Plan within the core network. A new Message “LCLS-NOTIFICATION” and a new IE “LCLS-Status” can thus be introduced. The LCLS-Status IE can be sent in the Assignment Acknowledgment message and in the new LCLS-Notification message, whenever it is necessary to inform the CN about a change in the LCLS-Status.
[00213] Assignment requests allow to determine the feasibility for LCLS within the BSS. But at that time, tUser still hasn't accepted the call and the User Plan shouldn't be connected yet. Connect information is dependent on the REL-8 not sent to the BSS, but only to the MS. Therefore, a new “A-CONNECT” Message can be introduced from the CN to the BSS.
[00214] There are situations where one MSC is upgraded to LCLS and the other MSC is not yet upgraded. The implementation thus takes the “MSC-LCLS-Capability” of each node into consideration. There are situations where the User Plan is required within the CN, eg. where LCLS is not allowed, but only one of the MSCs knows about it. Here, the “LCLS-MSC-Preference” of each node must be taken into account. Possibilities for negotiating LCLS-Capability and LCLS-Acceptance between oMSC and tMSC are given hereafter.
[00215] One option is that the common BSS (if it exists) informs both oMSC and tMSC about its BSS-LCLS-Capability, eg. in a new IE as outlined above. Both MSCs, oMSC and tMSC, inform this BSS about their individual MSC-LCLS-Capability and their individual MSC-LCLS-Preference in the Assignment Request. In this way no additional requests between MSCs may be necessary considering LCLS-Negotiation. The combination of all necessary information can then only be done within the BSS, which controls both sides of the call. This is illustrated in Fig. 11. The advantage of this option is the simplicity of the Nc interface. The downside is that neither oMSC nor tMSC has a complete overview involving LCLS-Capabilities and status. They don't know at the first stage that identical BSS is used on both sides of the call. They can be informed later by the BSS that LCLS is doable and/or established.
Consequently, the present implementation uses LCLS signaling between the oMSC and the tMSC by including an information element in a connection establishment signaling in the core network, as illustrated in Fig. 12. The oMSC informs the tMSC about the oBSS -LCLS- Capability and its own oMSC-LCLS-Capabilities and its own oMSC-LCLS-Preference. A new IE “LCLS-CN” can be exchanged between oMSC and tMSC in the forward direction on the Nc Interface to signal the “LCLS-Capability and LCLS-Preference”. The same IE can also be useful in the backward direction. Then it can also include the effective “LCLS-Status”. Possible contents and structure of such an information element (herein referred to as “LCLS-CN”) are discussed in detail above. The implementation requires only slightly more signaling effort at Nc. The advantage of this implementation is that tMSC knows at a very early stage whether LCLS is a candidate or not. An additional advantage is that at any time during the call, this new IE could be used to signal changes in LCLS-Capability, LCLS-Preference and LCLS-Status. An additional advantage is seen in call scenarios with more than one MSCs in the forwarding path (i.e. signaling path). Additional MSCs along the way can introduce their LCLS-Capability and/or LCLS-Preference in the information element, i.e. their needs to access the media plan.
[00217] In an example implementation, a new IE “LCLS-CN” is introduced, with a fixed length of one octet. If BICC or ISUP is used in Nc, then the IE of LCLS-CN is sent within IAM Message (Setup message) in forward direction within Mobile APM Message (Reply message) in reverse direction. IF SIP-I is used in the Nc, then the IE from LCLS-CN can be sent in a separate SIP header or inside the IAM encapsulated in the SIP invite in the forward direction, and in a separate SIP header or mobile ISUP APM encapsulated in the SIP response in the backward direction.
[00218] Typically, the oMSC does not know anything about tBSS; tMSC doesn't know anything about the BSS, i.e. the MSCs don't care, if the identical BSS is used on both sides of the call. But the MSCs know the identity of the call, at least indirectly. On the other hand the BSS typically does not care which sides of the call a call belongs to. BSS does not know a global call identity. The BSS only knows the identity of each side of the call (CIC or AoIP Caller Identifier). Again two different options exist to solve this problem and to match RAN Identity and Call Identity.
[00219] In a first option, MSCs inform each other that RAN is used: if oRAN and tRAN are identical, then MSCs recognize that LCLS is feasible. Unique RAN identities can be defined and exchanged, new CN signaling can be required. This option requires defining and maintaining globally unique RAN identifiers; this allows to some extent identify the location of the other user (personal data security issue); this also requires additional signaling through the core network in the case of switching without loss of inter-RAN communication.
[00220] In a second option, the MSCs define and negotiate a unique Caller ID for the call, which is then known to all nodes on the forwarding path. In complex calling scenarios, this CallerID can be globally (i.e. worldwide) unique. Then the MSCs inform the RAN(s) about the Global Caller ID on each side of the call: if the Caller IDs of oMS and tMS are identical, then the RAN recognizes that the call originates and ends in the same BSS and therefore LCLS is doable. These options use the definition and switch d in a Globally Unique Caller ID mode, which means new CN and new A Interface signaling. This option has particular advantages over call scenarios with more than two MSCs in the forwarding path.
[00221] Such a unique call identifier is specified in the ITU-T Q.1902 series, called “Global Call Reference” (GCR). GCR is unique worldwide, also across network boundaries. This GCR was introduced for charging purposes in complex calling scenarios. A possible parameter sketch of this Global Call Reference is shown in the following table:

[00222] The maximum length of this IE, including the length indicators, is 13 octets. In general all call sides that belong to a call use the same Global Call Reference. This includes, but is not limited to, Call Forwarding, Guest Connection from another network, Forwarding or Reselection. The GCR of the call will also be sent by the Anchor MSC on the IAM (ISUP / BICC) on call-side lossless switching/re-allocation towards the Non-anchor MSC. The nodes on the call path to the new MS location will then receive and be able to use this GCR.
[00223] The already specified Global Call Reference can be used for LCLS both within the CN and between CN and RAN. The oMSC generates a “Global Call Reference” (GCR) when it receives the Service Request from the oMS. This GCR is then sent along the forwarding path, finally arriving at the tMSC. All nodes on the path have the opportunity to pay attention to this GCR. This GCR is held until the call is terminated. OMSC sends this GCR within the oAssignment-Request to the oBSS for the oCall-leg; it's stored there; tMSC sends this GCR within tAssignment-Request to tBSS for tCall-leg; it's stored there, too. Both oMSC and tMSC send in addition their LCLS-Capability and LCLS-Preference to oBSS and tBSS in Assignment.
[00224] Then tBSS correlates the received GCR for tCall-leg with all stored GCRs and finds the corresponding oCall-leg for LCLS, if oBSS and tBSS are identical. If successful, then tBSS marks both sides of the call with “LCLS identified”. tBSS reports the correlation result for tMSC in the tAssignment-Response. At the same time oBSS (which is identical to tBSS) notifies that LCLS-Status to oMSC. Then the preparation for LCLS is finished. But LCLS is not yet in place to prevent a very early connection from the User Plan user, which could encourage fraud.
[00225] The MSC(s) can perform the following procedure to control the user plan connection. Assume the call is still in the call establishment phase. tMS initiates ring tone and oMS receives and performs ring back tone. The User Plan is established end-to-end in both directions through the core network, but traffic is blocked on oMGW and tMGW. A direct local shortcut within the BSS will bypass the user plan's connectivity control in the CN and will therefore allow fraudulent user data to pass before the response/change. It will also bypass the User Plan Plan between callback tone generated by tMGW and oMS. BSS can determine the correct point in time to establish LCLS as follows.
[00226] Without new signaling on Interface A, this can be achieved by “sniffing” in the DTAP signaling between MSC and MS.
[00227] Another possibility is to use a new procedure, message and IE that can inform the BSS when “Connect”. This procedure can be called “A-Connect”, the message can be called “A-CONNECT” and IE can be called “A-Connect-Control”. The trigger for this A-Connect procedure can be the “Connect” message from tMS, which is seen by tMSC and oMSC. Both tMSC and oMSC send the new A-CONNECT message to both tBSS and oBSS respectively. The content, i.e. the coding of the IE A-Connect-Control can in general be identical on both A-Interfaces, but it could also be different. If both sides of the call receive an explicit A-CONNECT message and the content allows LCLS, then BSS establishes LCLS. The calling side of tBSS catches the tA-CONNECT message in general sooner than the calling side of OBSS catches the oA-CONNECT message. But neither tBSS nor oBSS can acknowledge this message before the LCLS status is cleared, i.e. not before both sides of the call get the A-CONNECT message and LCLS is established - or it can be clarified that LCLS may not be established.
[00228] It should be clear that the general teachings given above can be applied to the specific implementations described here. In particular, the different methods of collecting media plane access needs, establishing the media plane and detecting legacy nodes in the signaling path can be applied to specific implementations. The Qualified Person will note that the features of the above aspects, embodiments and implementations of the invention may be combined from other embodiments which are within the scope of the present invention.
[00229] While specific embodiments of the invention are disclosed herein, various changes and modifications can be made without departing from the scope of the invention. The modalities presented are to be considered in all respects as illustrative and not restrictive, and all changes being within the range of meaning and equivalence of the appended claims are intended to be adopted herein.

权利要求:
Claims (32)
[0001]
1. Method for establishing a connection between a source terminal (T0) and a destination terminal (Tt) connecting through the same access network (101), the access network (101) accessing a core network (102) through an origin access connection point (110) to the origin terminal (TO), characterized in that it comprises the steps of: - at the origin access connection point (110), including an information element ( 2oo) in a setup message to establish the connection at least through the core network (1o2),- transmitting the setup message in a signaling path at least through the core network (1o2) to an access connection point of destination (12th) in the core network, in which at least one of the nodes (11th, 12th, 13th) through which a signaling path progresses enters information into the information element relating its needs to access a media plan ( 1o6) of the connection to be established, - receive at point d and destination access connection (12o) the setup message comprising the information element (2oo), - transmitting a response message including an information element (2oo) with the media plane access needs collected in an opposite direction along a signaling path to the source access connection point (11o), - provide information about the media plane access needs collected by the information element (2oo) to determine whether a local shortcut of a path of media (15o) of the mentioned connection can be established in the access network (1o1).
[0002]
2. Method according to claim 1, characterized in that the nodes (110, 120, 130) in the signaling path that are capable of processing an information element (200) adapt the media routing through their respective points connection network (MGW) on the basis of their own media plan access needs and the media plan access needs of the other nodes (110, 120, 130) in the signaling path indicated in the information element of the message mentioned establishment and/or the mentioned reply message.
[0003]
3. Method according to claim 1 or 2, characterized in that it further comprises the step of: - at the source connection point, verifying whether the source terminal and the destination terminal connect via the same access network retrieving information from a common visitor location record (VLR) storing information about the terminals connecting via the aforementioned access network or receiving information about the terminals connecting via the access network from a control node of the network of access, in which an element of information is included in the mentioned set-up message only if the origin and destination terminals connect via the same access network.
[0004]
4. Method according to any one of claims 1 to 3, characterized in that said media path (150) comprises a front channel (151) and a rear channel (152), the information element (200) comprising at least the following elements indicating a need to access the media plane: an element indicating a need to read the front channel (AR), an element indicating a need to write the front channel (Aw), an element indicating a need to read the rear channel (BR), and an element indicating a need to write in the rear channel (Bw).
[0005]
5. Method according to any one of claims 1 to 4, characterized in that an information element (200) comprises elements (AR, AW, BR, BW) in the form of flags to store access needs to the media plan , the input of information by a node into an information element comprising stabilizing the flag for the corresponding need to access the media path.
[0006]
6. Method according to any one of claims 1 to 5, characterized in that in the information element, the media plan access needs of each node that introduced such information are stored separately in association with a node identifier for the respective node.
[0007]
7. Method according to claim 5, characterized in that each node entering information in the information element is setting the same flag for each need to access the media plane, the setting of the flags being carried out such that a flag that has been configured by one node and reconfigured by another node in order to obtain accumulated information about the media plane access needs of nodes along a signaling path in the mentioned information element.
[0008]
8. Method according to any one of claims 1 to 7, characterized in that it comprises the steps of: - at each node (110, 120, 130) in the signaling path, establishing the context of the media connection point and links the media connection point (MGW) associated so as to establish the media path at least through the core network (102) upon receipt of the set-up message and/or the response message; and - on the basis of accumulated media plane access needs, determine whether media contents are to be transmitted on the configured media path at least through the core network (102).
[0009]
9. Method according to any one of claims 1 to 7, characterized in that it further comprises the step of:- at each node (110, 120, 130) in the signaling path, establish context of the media connection point and links of the media connection point (MGW) associated so as to establish the media path at least through the core network (102) when receiving the setup message and/or the reply message, where nodes in the signaling path capable of processing an information element (200) are allowed to decide to establish an uplink or downlink of the media path (150) to passivate in dependence on the media plane access needs the upstream and downstream nodes of the signaling path, with a passive link meaning that resources for the link are allocated so no content is transmitted over the link.
[0010]
10. Method according to claim 9, characterized in that the media path (150) comprises a front channel (151) and a rear channel (152), the method further comprises the steps of:- including at the point of destination access connection an additional information element in the response message, - by at least one of the nodes through which a signaling path progresses, introduce information relating its need to access the media plane (106) in the information element additional to the response message, wherein each node (110, 120, 130) in the signaling path allowed to process the information element is still performing the steps of determining from the information element (200) received with the message. establishing whether any node downstream of the rear channel (152) has media plane access needs for the rear channel (152), and if no media plane access needs are detected, establishing the corresponding and media connection point for the downstream back channel to passive; - determine from the additional information element received with the response message whether any node downstream of the front channel (152) has a need for access to the media plane for the front channel (152), and if no media plane access needs are detected, establish the corresponding media connection point for the downstream front channel to passive.
[0011]
11. Method according to any one of claims 8 to 10, characterized in that it comprises the step of:- transmitting a heartbeat signal through the links of the media path through which no media content is transmitted, or disabling detection of whether media content is transmitted over these links in the corresponding media context managers of the media connection points providing these links.
[0012]
12. Method according to any one of claims 1 to 7, characterized in that the media path (150) comprises a front channel (151) and a rear channel (152), the method further comprising the steps of:- including at the destination access connection point an additional information element in the response message, by at least one of the nodes through which a signaling path progresses, introduce information relating its need to access the media plane (106) in the additional information element of the response message, wherein each node (110, 120, 130) in the signaling path enabled to process an information element is further configured to establish the media path (150) according to an information element and an additional information element such that if the node determines that any node in the downstream front channel or rear channel (151, 152) signaling path has no need to access the media plane for the respective. the channel, then the node does not establish a link from the media path to the next node downstream of the respective channel, or removes a link from the media path established to the next node downstream of the respective channel.
[0013]
13. Method according to any one of claims 1 to 12, characterized in that the method further comprises a detection of legacy network nodes in the signaling path not capable of processing an information element (200) including a field of node identification in an information element (200), with each node in the signaling path capable of processing the information element, performing the steps of verifying whether a node identifier is stored in the node identification field of an information element (200) received with the aforementioned establishment message matches a node identifier from which the message was received; - if the node identifiers do not match, establish total need for access to the media plane in the information element (200 ); and - write the proper node identifier in the node identification field of the information element.
[0014]
14. Method according to any one of claims 1 to 6, characterized in that an information element comprises a list of access needs in which each node of the signaling path capable of processing the information element (200) introduces its need for access to the media plane and a node identifier, and where nodes in the signaling path capable of processing an information element (200) are configured to establish the media path (150) through the nodes having a need for media plane access configuring a direct connection to the next upstream or downstream node that has a media plane access need, such that the media path (150) bypasses the media connection point from nodes other than the source and destination access connection points (110, 120) having no need to access the media plan.
[0015]
15. Method according to claim 14, characterized in that each node (110, 120, 130) in the signaling path capable of processing the information element and having a need to access the media plane performs the steps of: - receiving the response message comprising the information element (200) with the list of access needs; - scanning a list comprised in the response message to the first node downstream or upstream in the signaling path that has an access need to the media plane;- establish a media path connection to the first mentioned node or change an existing media path connection in order to connect to the first mentioned node, if such a node is found, to establish the media path by less on the core network.
[0016]
16. Method according to claim 14 or 15, characterized in that it further comprises the steps of: - detecting legacy nodes not able to process the information element in the signaling path by means of an information element; - if a or more legacy nodes are detected, establishing media path connections to the first enabled upstream node and the first enabled upstream node the legacy node in the signaling path establishing media path connections by said first upstream and downstream node to legacy nodes in order to establish the media path through said legacy node.
[0017]
17. Method according to any one of claims 1 to 16, characterized in that it further comprises the steps of: - evaluating the information on the need for access of the media plan collected with the information element (200) in order to determine whether said local path of media path (150) in the access network (101) can be established; and - if a shortcut can be established, inform a controller (ACN) of the access network that a shortcut can be established or transmit information about the need for access to the media plane to said controller (ACN).
[0018]
18. Method for establishing a connection between a source terminal (T0) and a destination terminal (T1) connecting through the same access network (101), the access network (101) accessing a core network (102) through of at least one access connection point (110, 120), the method being performed by the core network node (130) of the aforementioned core network (102), the method characterized in that it comprises the steps of:- receiving connection establishment signaling for establishing said connection, said signaling being transmitted along a signaling path in at least one core network (102), said core network node (130) being in the signaling path; - receiving with a mentioned connection establishment signaling an information element (200) storing the media plane access needs of at least one node (110, 120, 130) preceding the mentioned core network node in the signaling path mentioned with respect to the transmission direction of the information element (200), wherein said media plane access needs indicate the needs of a preceding node to access a media plane (106) of the connection to be established, - introduce information related to the need of the core network node (130) to access the media plane in the information element (200), - transmit the information element (200) with a mentioned connection establishment signaling to a next node in the signaling path in order to enable the collection of media plane access needs from the nodes in the signaling path through the mentioned information element (200) to determine whether a current h the location of a media path (150) of the mentioned connection can be established in the access network (101).
[0019]
19. Method according to claim 18, characterized in that it further comprises the steps of: - adapting the media forwarding through a media connection point of the core network node mentioned in the bases of access needs to the plan media of the core network node and the need to access the media plane of the other nodes (110, 120, 130) in the signaling path indicated in the information element received with a mentioned connection establishment signaling and/or in the corresponding element of information comprised in a message received in response to connection establishment signaling.
[0020]
20. Method according to claim 18 or 19, characterized in that the media path (150) comprises a front channel (151) and a rear channel (152), the method further comprising the steps of:- receiving in a response message to said connection establishment signaling an additional information element storing the media plane access needs of at least one node (110, 120, 130) preceding the mentioned core network node in said signaling path with respect to a transmission direction of an additional information element (200), - determine from the said information element and the said additional information element whether any nodes in the signaling path have media plane access needs for the front channel or to the rear channel, - establish media connection point context and links of a media connection point (MGW) associated with the core network node in order to establish the media path through the core network, and that if it is determined from the information element that there is no need to transport media content in the downstream or forward direction channel, the downstream media link for the respective channel is not established or, if previously established, removed, or the downstream media link for the respective channel is set to passive meaning that no content is transmitted over the media link.
[0021]
21. Method according to claim 18 or 19, characterized in that the information element comprises a list of access needs in which each node of the signaling path capable of processing the information element (200) enters its needs for access to the media plane and a node identifier, in which, if the core network node has its own need to access the media plane, the method further comprises the steps of:- receiving a response message for signaling mentioned connection establishment comprising information element (200) with the list of access needs; - scanning the list comprised in the response message to the first downstream or upstream node in the signaling path that has an access need in the media plane ;- establish a connection in the media path to the first mentioned node or change a connection in the existing media path in order to connect to the first mentioned node, if such a node is found, to establish the media path at least on the core network.
[0022]
22. Method according to any one of claims 18 to 21, characterized in that the information element is configured as defined in any one of claims 4 to 7.
[0023]
23. Network node for a core network adapted to establish a connection between a source terminal (T0) and a destination terminal (Tt) connecting through the same access network (101), the access network (101) accessing said core network (102) via at least one access connection point (110, 120), the core network node (130) is characterized in that it is configured to perform the steps of:24. receiving connection establishment signaling to establish said connection, said signaling being transmitted along a signaling path at least in the core network, said core network node (130) being in said signaling path,25. receive with a mentioned connection establishment signaling an information element (200) storing the media plane access needs of at least one node preceding the node of the core network mentioned in the mentioned signaling path with respect to the transmission direction of an information element, and that the media plane access needs indicate the needs of a preceding node to have access to the media plane (106) of the connection to be established,26. introduce information relating to the need for the core network node (130) to have access to the media plane in the information element (200),27. transmit the information element (200) with a mentioned connection establishment signaling to a next node on the signaling path in order to enable the collection of media plane access needs of the nodes on the signaling path via the information element (200) mentioned to determine whether a local path of a media path (150) of the mentioned connection can be established in the access network (101).
[0024]
24. Network node for a core network according to claim 23, characterized in that the network node is configured to perform method as defined in any one of claims 19 to 22.
[0025]
25. Method for establishing a connection between a source terminal (T0) and a destination terminal (T1) connecting through the same access network (101), the access network accessing a core network (102) through at least one access connection point (110, 120), the method being performed by the access connection point (110, 120) and characterized in that it comprises the steps of:- receiving connection establishment signaling to establish said connection , a said signaling being transmitted along a signaling path at least in the core network (102), - collecting information about the needs of nodes in the said signaling path to have access to the media plane (106) of the connection to be established , the information being collected by retrieving an information element (200) from the received connection establishment signaling, from said information element storing the media plane access needs of at least one of the nodes in the signaling path, - providing the information about the media plane access needs collected by the information element (200) to determine whether a local path of a media path (150) of the mentioned connection can be established in the access network (101).
[0026]
26. Method according to claim 25, characterized in that the access connection point is an originating access connection point (110) through which the core network (102) is accessed for the originating terminal (T0), said method further comprises:- including an information element (200) in the setup message to establish the connection at least through the core network (102), and- transmitting the setup message in a signaling path at least through the core network (102) to a destination access connection point (120) in the core network (102), the received connection establishment signaling being a response message transmitted by the access connection point of destination (120) in response to the set-up message, said reply message comprising the information element (200) of the set-up message into which at least one of the nodes along the signaling path has introduced its needs access to the media plan.
[0027]
27. Method according to claim 25 or 26, characterized in that the access connection point is a destination access connection point (120) through which the core network (102) is accessed for the terminal of destination (Tt), and that a mentioned received connection set up signaling is a set up message transmitted by an originating access connection point (110) of the core network (102) along a signaling path, the Said setup message comprising said information element (200) in which at least one of the nodes along a signaling path has introduced its access needs to the media plane, the method further comprises transmitting a response message including the element of information (200) with media plane access needs collected in an opposite direction along the signaling path to the source access connection point (110).
[0028]
28. Method according to any one of claims 25 to 27, characterized in that the information element is configured as defined in any one of claims 4 to 7.
[0029]
29. Access connection point of a core network adapted to establish a connection between a source terminal (T0) and a destination terminal (Tt) connecting through the same access network (101), the connection point of access (110, 120) being adapted to provide access to a core network (102) for the access network (101), the access connection point characterized in that it is configured to perform the steps of:30. receiving connection establishment signaling to establish said connection, said signaling being transmitted along a signaling path at least in the core network (102),31. collect information about the needs of nodes in the mentioned signaling path to have access to the media plane (106) of the connection to be established, the information being collected by retrieving an information element (200) of the received connection establishment signaling, the element of information (200) mentioned storing the media plane access needs of at least one of the nodes in the signaling path32. providing information about the media plane access needs collected by the information element (200) to determine whether a local path of a media path (150) of the mentioned connection can be established in the access network (101).
[0030]
30. Access connection point according to claim 29, characterized in that the access connection point is configured to carry out the method as defined in any one of claims 26 to 28.
[0031]
31. Electronically readable data carrier with stored electronically readable control information, characterized in that it is established such that when using the data carrier in a computer system, the control information performs a method as defined in any one of claims 1 to 22 and 25 to 28.
[0032]
32. A computer-readable storage medium, characterized in that it contains computer-readable instructions which, when read by a computer, cause the computer to perform the method as defined in any one of claims 1 to 22 and 25 to 28 .

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012003294B1|2021-06-22|METHOD FOR ESTABLISHING A CONNECTION BETWEEN A SOURCE TERMINAL AND A DESTINATION TERMINAL, NETWORK NODE TO A CORE NETWORK, ACCESS CONNECTION POINT OF A CORE NETWORK, HOLDER OF ELECTRONICALLY LEGIBLE DATA, AND, COMPUTING STORAGE MEANS

---

US10616818B2|2020-04-07|System and method for speeding call originations to a variety of devices using intelligent predictive techniques for half-call routing

---

US10567930B2|2020-02-18|System and method for enabling call originations using SMS and hotline capabilities

---

US9622078B2|2017-04-11|Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks

---

US9763164B2|2017-09-12|System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network

---

US6490451B1|2002-12-03|System and method for providing packet-switched telephony

---

KR20090007615A|2009-01-19|Call delivery to a dual mode wireless device

---

CN1889756B|2010-05-12|Method for double-mode terminal switching between block field and circuit field

---

US20100008353A1|2010-01-14|Method and system for ending-call anchoring of circuit switched domain

---

CN108476448A|2018-08-31|A kind of method for processing business and device

---

EP3086581B1|2019-07-17|Call control device and method for processing user services

---

JP5175934B2|2013-04-03|Using WLAN for Media Transfer in Cellular Mobile Network

---

EP1076462A2|2001-02-14|Architecture to support service features for wireless calls in a wireless telecommunication system

---

US9609622B2|2017-03-28|Provision of a customised alerting notification

---

KR101529972B1|2015-06-18|Method and apparatus for reprocessing call and method for servicing call waiting tone

---

JP5178944B2|2013-04-10|Using WLAN for Media Transfer in Cellular Mobile Network

---

EP3035627A1|2016-06-22|Method of providing coverage extension to an existing mobile network, and corresponding system.

---

WO2009092437A1|2009-07-30|Completion of fax and analog data call

---

CN106850625A|2017-06-13|Signalling flow distributing method and device

同族专利:

---

公开号 | 公开日

---

IN2012DN00873A|2015-07-10|

---

AU2010283719B2|2012-10-04|

---

US8634838B2|2014-01-21|

---

EP2465323A1|2012-06-20|

---

AU2010283719A1|2012-03-08|

---

CN102484884A|2012-05-30|

---

JP2013502125A|2013-01-17|

---

WO2011018524A1|2011-02-17|

---

EP2465323B1|2015-10-07|

---

CN102484884B|2015-06-17|

---

US9060350B2|2015-06-16|

---

JP5650220B2|2015-01-07|

---

US20120270554A1|2012-10-25|

---

US20140169294A1|2014-06-19|

---

BR112012003294A2|2020-10-27|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

JP2000022710A|1998-07-03|2000-01-21|Fujitsu Ltd|Path setting method, communication device and storage medium|

---

EP1158823A1|2000-05-22|2001-11-28|TELEFONAKTIEBOLAGET LM ERICSSON |Method for a connection through a core network|

---

WO2004002177A1|2002-06-25|2003-12-31|Nokia Corporation|Routing method and network element|

---

GB0326160D0|2003-11-08|2003-12-17|Marconi Comm Ltd|Call set-up systems|

---

JP4728931B2|2006-11-08|2011-07-20|株式会社エヌ・ティ・ティ・ドコモ|Mobile communication system, radio control apparatus, extension transmission / reception server apparatus selection method|

---

EP2059087A1|2007-11-06|2009-05-13|Nokia Siemens Networks S.p.A.|Method for establishing circuit switched calls in a mobile radio network and mobile radio network|

---

CN101159905B|2007-11-07|2010-04-21|华为技术有限公司|Local exchange method, core network equipment and network system of implementing in base station controller|

---

CA2732148C|2008-07-28|2018-06-05|Digifonica Limited|Mobile gateway|

---

CN101998666B|2009-08-12|2014-09-10|中兴通讯股份有限公司|Method for realizing local call and local exchange|

---

WO2012121644A1|2011-03-04|2012-09-13|Telefonaktiebolaget L M Ericsson |Local call local switching at handover|

---

US8774168B2|2011-04-14|2014-07-08|Skype|Communication system and method|US9756874B2|2011-07-11|2017-09-12|Proteus Digital Health, Inc.|Masticable ingestible product and communication system therefor|

---

JP2008539047A|2005-04-28|2008-11-13|プロテウスバイオメディカルインコーポレイテッド|Pharma Informatics System|

---

US8802183B2|2005-04-28|2014-08-12|Proteus Digital Health, Inc.|Communication system with enhanced partial power source and method of manufacturing same|

---

JP5916277B2|2006-10-25|2016-05-11|プロテウス デジタル ヘルス， インコーポレイテッド|Ingestible control activation identifier|

---

CN101584166A|2006-11-02|2009-11-18|迪吉福尼卡（国际）有限公司|Producing routing messages for voice over IP communications|

---

US8422507B2|2006-11-29|2013-04-16|DigifonicaLimited|Intercepting voice over IP communications and other data communications|

---

KR101475666B1|2007-02-01|2014-12-23|프로테우스 디지털 헬스, 인코포레이티드|ingestible event marker systems|

---

US8537805B2|2007-03-26|2013-09-17|DigifonicaLimited|Emergency assistance calling for voice over IP communications systems|

---

US8540632B2|2007-05-24|2013-09-24|Proteus Digital Health, Inc.|Low profile antenna for in body device|

---

SG195535A1|2008-07-08|2013-12-30|Proteus Digital Health Inc|Ingestible event marker data framework|

---

CA2732148C|2008-07-28|2018-06-05|DigifonicaLimited|Mobile gateway|

---

US9659423B2|2008-12-15|2017-05-23|Proteus Digital Health, Inc.|Personal authentication apparatus system and method|

---

JP6498177B2|2013-03-15|2019-04-10|プロテウス デジタル ヘルス， インコーポレイテッド|Identity authentication system and method|

---

SG196787A1|2009-01-06|2014-02-13|Proteus Digital Health Inc|Ingestion-related biofeedback and personalized medical therapy method and system|

---

EP2424427B1|2009-04-28|2021-06-16|Otsuka Pharmaceutical Co., Ltd.|Highly reliable ingestible event markers|

---

PL2478678T3|2009-09-17|2016-05-31|Digifonica Int Ltd|Uninterrupted transmission of internet protocol transmissions during endpoint changes|

---

TWI517050B|2009-11-04|2016-01-11|普羅托斯數位健康公司|System for supply chain management|

---

CN102065406B|2009-11-12|2014-04-09|中兴通讯股份有限公司|Implementation method for local switch of local call|

---

RU2587795C2|2010-02-01|2016-06-20|Проутьюс Диджитал Хэлс, Инк.|Data collection system|

---

CN101772221B|2010-02-05|2014-12-31|中兴通讯股份有限公司|Method for finishing smooth cleft grafting and cleft grafting operation executing equipment and devices|

---

CA2795746C|2010-04-07|2019-10-01|Timothy Robertson|Miniature ingestible device|

---

CN102238662B|2010-04-30|2015-12-16|中兴通讯股份有限公司|A kind of method and system and base station sub-system realizing switching in local exchange|

---

TWI557672B|2010-05-19|2016-11-11|波提亞斯數位康健公司|Computer system and computer-implemented method to track medication from manufacturer to a patient, apparatus and method for confirming delivery of medication to a patient, patient interface device|

---

CN101854717A|2010-06-09|2010-10-06|中兴通讯股份有限公司|Data transmission method, user equipment and base station|

---

EP2606673B1|2010-08-17|2018-07-04|Telefonaktiebolaget LM Ericsson |NODE AND METHOD FOR AoIP ADDRESS CHANGE|

---

EP2666333B1|2011-01-19|2014-11-05|Telefonaktiebolaget LM Ericsson |Local data bi-casting between core network and radio access network|

---

WO2012121644A1|2011-03-04|2012-09-13|Telefonaktiebolaget L M Ericsson |Local call local switching at handover|

---

US8687640B2|2011-03-22|2014-04-01|Metaswitch Networks Ltd.|Controlling communication sessions|

---

CA2842952C|2011-07-21|2019-01-08|Proteus Digital Health, Inc.|Mobile communication device, system, and method|

---

JP5854793B2|2011-11-25|2016-02-09|キヤノン株式会社|COMMUNICATION DEVICE, ITS CONTROL METHOD, AND CONTROL PROGRAM|

---

US11149123B2|2013-01-29|2021-10-19|Otsuka Pharmaceutical Co., Ltd.|Highly-swellable polymeric films and compositions comprising the same|

---

WO2014117858A1|2013-02-01|2014-08-07|Nokia Solutions And Networks Oy|Management of radio resource control for device-to-device communication|

---

JP5941240B2|2013-03-15|2016-06-29|プロテウス デジタル ヘルス， インコーポレイテッド|Metal detector device, system and method|

---

US9796576B2|2013-08-30|2017-10-24|Proteus Digital Health, Inc.|Container with electronically controlled interlock|

---

US9270503B2|2013-09-20|2016-02-23|Proteus Digital Health, Inc.|Methods, devices and systems for receiving and decoding a signal in the presence of noise using slices and warping|

---

US10084880B2|2013-11-04|2018-09-25|Proteus Digital Health, Inc.|Social media networking based on physiologic information|

---

US20150127738A1|2013-11-05|2015-05-07|Proteus Digital Health, Inc.|Bio-language based communication system|

---

WO2015112603A1|2014-01-21|2015-07-30|Proteus Digital Health, Inc.|Masticable ingestible product and communication system therefor|

---

US9854512B2|2014-05-13|2017-12-26|Sharp Kabushiki Kaisha|Terminal device and communication control method|

---

EP3151527A4|2014-05-28|2018-01-17|Sony Corporation|Apparatus and method|

---

US11051543B2|2015-07-21|2021-07-06|Otsuka Pharmaceutical Co. Ltd.|Alginate on adhesive bilayer laminate film|

---

JP6552148B1|2016-07-22|2019-07-31|プロテウス デジタル ヘルス， インコーポレイテッド|Electromagnetic sensing and detection of ingestible event markers|

---

GB2566051B|2017-08-31|2020-01-08|Metaswitch Networks Ltd|Media Bypass|

---

CN108390795B|2018-02-08|2021-03-19|广东美的制冷设备有限公司|Household appliance and monitoring method thereof, smart home system and readable storage medium|

---

CN112995232B|2021-05-19|2021-08-10|四川创智联恒科技有限公司|Optimization method for concurrent transmission of ORAN protocol data plane and control plane|

法律状态:
2020-11-10| B15K| Others concerning applications: alteration of classification|Free format text: A CLASSIFICACAO ANTERIOR ERA: H04W 76/02 Ipc: H04L 29/06 (2006.01), H04W 76/10 (2018.01), H04W 8 |

---

2020-11-10| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2021-05-18| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2021-06-22| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 13/08/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF, , QUE DETERMINA A ALTERACAO DO PRAZO DE CONCESSAO. |

优先权:

---

申请号 | 申请日 | 专利标题

---

US23406809P| true| 2009-08-14|2009-08-14|

---

US61/234068|2009-08-14|

---

US61/234,068|2009-08-14|

---

PCT/EP2010/061859|WO2011018524A1|2009-08-14|2010-08-13|Connection set-up between two terminals|

---